$PORT and process.env.PORT offset by 100

[rvangundy]

I'm starting a couple processes with Foreman. In my node.js process, I refer to process.env.PORT. In my Procfile, I use $PORT as a parameter to another process. My second process is only for debugging and basically processes some files and opens up my browser to the specified port (it's not using the port for anything else). So if I start Foreman with foreman start --port=5000, process.env.PORT is 5100 while $PORT is 5000. Shouldn't these be the same value?

[rvangundy]

Looking through the issues found pull #110 makes this behavior intentional. So my issue then is how to determine one process's assigned port from another process. Maybe outside the scope of Foreman altogether. Though I would like to hear some thoughts/suggestions as to how to handle this kind of thing in the context of Foreman.

[ddollar]

These should be the same value, any other behavior is likely a bug.

[ddollar]

If you'd like to create a pull request to address this I'd be happy to take a look. Thanks!

[RichardOrnelas]

I just now started to get this issue. i request port 8080 and foreman starts with 8180