Docker compose for different environment?

[khasburrahman66]

How usually docker compose is set for a different environment?
Currently I use two docker-compose file:

• (remote) one that includes nginx for ssl and exposes only the nginx to the outside
• (local) one that doesn’t include nginx, exposes the application

So it means, I have to maintain two kind of somewhat similar file. Is this approach expected? Or there are other approaches that better?

[meyay (Metin Y.)]

Same objective:

Docker-compose same config for dev and production but enable code sharing between host and container only in development

I’ve asked the same question on SO, but I feel that people from this forum are more concentrate on this topic. Here is the SO link, (link) and I’m coying the question here. As the most important benefit of using docker is to keep dev and prod env to be the same so let’s rule out the option of using two different docker-compose.yml Let’s say we have a Django application, and we use gunicorn to serve for production and we have a dedicated apache2 as a reverse proxy(this apache2 is out of dock…