Bug report: changes to Digital Ocean App Platform Procfile not picked up

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 but it looks like App Platform needs the process to listen on

So I updated the Procfile to this:

web: datasette -h -p $PORT

This failed to deploy as well - but the Deploy logs showed that my process was still running on!

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.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

@swillison 👋

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!