Hi all, I currently run a few applications on a DO droplet using docker compose (they’re all wrapped in Dockerfiles). I’d like to switch to the new App platform, but I’m wondering how I’d maintain dev/prod parity? I like that I can run docker-compose up to bring up a database, and the application containers in an environment that is almost identical to production. I’m worried that if I run ruby/php/etc locally, it won’t be configured the same way as it will be in production.
My assumption would be that DO provides docker images of the environment the applications are run on in production, but I’ve read that it actually uses buildpacks like Heroku. How do I achieve dev/prod parity with that?
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!
The App Platform can build from either Dockerfile, or if no Dockerfile is provided from buildpack. The App Platform will automatically detect and use a Dockerfile, named “Dockerfile”, in the root of your repository. You can also explicitly specify a path to a Dockerfile in the App Spec yaml applied by API or doctl.
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.