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?
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!
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.
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 AI-native businesses
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.