Should I use one docker-compose.yml for all my services?
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Hi,
I'm using docker-compose to host all my server services (jellyfin, qbittorrent, sonarr, etc.). I've recently grouped some of them into individual categories and then merged the individual docker-compose.yml file I had for each service into one per category. But is there actually any reason for not keeping them together?
The reason why is I've started configuring homepage and thought to myself "wouldn't it be cool if instead of giving the server IP each time (per configured service in homepage) I'd just use the service name?" (AFAIK this only works if the containers are all in the same file).
You are viewing a single comment
I have a folder that all my docker services are in. Inside the folder is a folder for each discrete service and within that folder is a unique compose file necessary to run the service. Also in the folder is all the storage folders for that service so it's completely portable, move the folder to any server and run it and you're golden. I shut down all the services with a script then I can just tar the whole docker folder and every service and its data is backed up and portable.
In case anyone cares here is my script, I use this for backups or shutting down the server.
This is exactly what I do and could not be happier!
Exactly my setup and for exactly the reasons you mentioned
Could you share your script?
Scroll down a bit, I added it later.
Thanks!
Does portainer just work?
To answer my own question, yes, yes it does. Should've done this ages ago...
@czardestructo I like the tidiness of this.
Exactly what I do except my master folder is
~