Default port on heroku local overrides .env about heroku-cli HOT 8 CLOSED

Thank you for letting us know. I would definitely classify this as a bug. I'll look into it this week.

from heroku-cli.

I just hit this port .env $PORT bug as well.

The needed fix to use latest heroku local felt weird: In my 'run' script, I had to grep the .env file for the $PORT value, then pass this to heroku local using the new --port option. But heroku local reads the .env file itself..

from heroku-cli.

Also, this bug was confusing to diagnose.

I finished coding yesterday and everything worked. I started coding today, and my server run via 'heroku local' was suddenly running on a different port.

I presume the heroku cli auto-updated itself in the interim..

from heroku-cli.

@greghuc Thank you for posting a workaround, we apologize for the inconvenience. Yes, it probably did autoupdate. We are currently evaluating solutions for this and hope to have a fix released soon.

from heroku-cli.

Hey @k80bowman, have you had a chance to look into this?

from heroku-cli.

@rlt I apologize for the delay, I'm in the process of working on it now.

from heroku-cli.

Great, thank you!

from heroku-cli.

Resolved by #2618

from heroku-cli.