Multiple instances of compose project with different enviroment setings

General
1

Hello community,

i have an docker-compose project that consist of 3 services.
and would like to start up this project with different environment settings.
currently we are planing at least for a production, development and test instance of the project.
for each the compose file itself could be the same (at least from our point of view)
but we would need some of the settings changed -
i am using environment variables and also secrets.

i found

i understand that they work a litte different -
is one or the other the best-practise for my need / something like this?

the follow up question for this is:
if i want to setup one of these project-instances for every customer, are there any tools to manage something like this - (this means >100 instances)?
or what is the best practice in this case?
or it is a very bad idea in generell because the meta ressource usage is to high with this meany containers?!
(and its better to setup the app in the container to handle the multiple instances) ?

i am new to this advanced usage of docker-compose -
so any tips or hints for extended tutorials / best-practice guides are highly welcome!

sunny greetings
stefan

2

What is meta resource usage? If it’s about container size, check if you can use a smaller base image, like an alpine or slim version.

3

with meta resource usage i mean disk usage / memory usage.
i will look into this some more…