How are folks using this in production?

[SHxKM]

First of all huge kudos to @nickjj for putting this out here. Big fan of Running in Production and not surprised to see this quality code here.

I was wondering, since all the "serverless" providers I checked (Heroku, fly.io, Railway) don't support docker-compose.yml (while most of them do support Dockerfiles), how are people deploying this stack to production?

[nickjj]

Hi,

You can run it on any server that you set up on any cloud provider or hardware you own. DigitalOcean is a popular provider but you can use any cloud hosting provider you're comfortable with.

The project is also compatible with Heroku. Folks have successfully deployed it. Here's an issue with the exact Heroku specific configs they added nickjj/docker-rails-example#70 (comment). It's for the Rails example app but it 100% applies to this app too.

I'm not sure about Fly, personally I wouldn't use that service. I've heard nothing but horror stories, especially around unreliability with Postgres.

[SHxKM]

Thanks @nickjj. Guess what I’m asking is given that most of those services support Dockerfiles but not docker compose, how’d that work? Also, in case I wanna run each service (or at least Postgres) in its own VM. Will dig some more in here. Thanks.

[nickjj]

The linked discussion from my comment goes over how Heroku handles their own config file which is comparable to a Docker Compose config. This project out of the box currently supports running Postgres or Redis or Celery on the same server or separate servers. You can control which services start up with the COMPOSE_PROFILES environment variable and all connection strings are configurable as well.