By Mike
The application I’m using uses the PORT variable for something else than the main listening port.
Why does setting the service’s HTTP port set the PORT environment variable and how can I avoid this? It seems completely absurd to force overwrite the PORT env variable. It makes my app unusable with the app platform.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi there,
As far as I know, there’s no way to prevent this behavior right now. App Platform assumes your app will listen on whatever is in PORT, and it injects that value at runtime to manage routing.
If your app uses PORT for something else, one workaround is to modify your app (if possible) to read the actual listening port from another variable, like APP_PORT, and map that manually in your code.
It’s worth reaching out to support to confirm if there’s any way around this: https://do.co/support
And might be a good idea to suggest it as a feature here too: https://ideas.digitalocean.com/
- Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.