App platform release step?

Looking to play around a bit with the new PaaS app platform.

I don’t see any concept of a “release phase” (see heroku) where one would typically trigger things like database migrations, and cancel the new code being released if it fails.

I could include in the run command (migrate + run) but it’s not clear from the docs how that would behave if multiple containers tried to execute it at the same time, or what would happen if it fails.

What is the recommended approach for doing database migrations like this?

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

👋 @theozero

Great question, we do not currently have a similar feature but, one is being worked on (I’m working on it) which will allow for pre and post deploy jobs to run before or after an app is deployed.

At this time, combining the migrate and startup of your app as you mentioned is the best option.

Stay tuned for the jobs feature release.