By swillison
I’m trying out App Platform. I stared with a Procfile that looks like this:
web: datasette -p $PORT
(And a requirements.txt that listed datasette)
This failed to deploy because the healthcheck failed - Datasette defaults to listening on 127.0.0.1 but it looks like App Platform needs the process to listen on 0.0.0.0
So I updated the Procfile to this:
web: datasette -h 0.0.0.0 -p $PORT
This failed to deploy as well - but the Deploy logs showed that my process was still running on http://127.0.0.1:8080!
After some digging around I found that the “Run Command” listed in the “Components” tab had persisted the original value from my Procfile. Updating that value using the web UI fixed the problem.
So my bug report / feature request is that if I modify the Procfile in my repository I would like the “Run Command” to be automatically updated to reflect that change.
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!
Thanks for surfacing this bug. We shouldn’t be persisting the initial Procfile command on the spec when the app is created. We’ll get that fixed ASAP.
Glad you were able to figure out the solution of removing the custom run command from your app spec. Happy coding!
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.