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?

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.

×
1 answer

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.

  • Thanks, but I’d like to use the buildpack in production rather than maintaining my own Dockerfile (it’s just a vanilla rails app). My question is how to run the environment locally for development (e.g. run the buildpack locally).

Submit an Answer