-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nor .env or environment variable PORT is used as port #17
Comments
I'm working on this at https://github.com/alej0varas/honcho |
I have a related problem, which is that there seem to be some automatic PORT incrementing going on (https://github.com/nickstenning/honcho/blob/master/honcho/command.py#L171), which makes honcho hard to use with heroku which kills processes that listens on any other port than the one specified in $PORT. Also, it's a behavior that is different from foreman. |
No, that's exactly what honcho is meant to do, and it's exactly what foreman does too:
The Heroku stack has a native understanding of the Procfile format, and you shouldn't need to use either honcho or foreman directly. See the Heroku documentation for further information. Closing. |
Hi! I've now investigated this a little more, and of course found out that the port incrementing is done by both foreman as well. Sorry for the assumption that this was wrong. However, I believe I've managed to find a difference with the $PORT between foreman and honcho. If i use -p 5000, Foreman seems to consistently set the $PORT variable for the first process of the first process type to 5000, while the process that gets assigned the 5000 port with honcho seems more random. The following Procfile
Results in the following output with foreman:
And the following with honcho:
If you're running honcho/foreman on Heroku (and I know this is unorthodox, but there are scenarios where this can be beneficial) it's good to have a deterministic way that the $PORT gets assigned. |
This issue is known and has been addressed in the master branch. See issue #13. If you have additional problems, would you mind filing separate tickets rather than using this one as a forum for discussion? Thank you! |
I believed the problem I saw was related to this issue, otherwise I wouldn't have posted here. I jumped to conclusions that was wrong, and I'm very sorry about that. I never meant to use this one as a forum, or to waste your time. Sorry =/. |
No need to be sorry, and sorry if my last comment sounded curt. It was just composed on a train, that's all =). You're not wasting my time, and not to worry about this ticket! |
This ticket saved me another hour of debugging. For those interested: https://ddollar.github.io/foreman/#PROCFILE
|
While environment variable PORT is set to 8000 or a .env file containing PORT=8000 exists, honcho still use 5000 as the port value.
The text was updated successfully, but these errors were encountered: