Should I use one docker-compose.yml for all my services?
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).
i go so far the other way with this personally.. I actually have a seperate LXC for each docker container and a lot of the time i use docker run instead of docker-compose..
I've still not had anyone explain to me why compose is better than a single command line..
I always thought the compose file is great for maintenance. You can always save the docker run commands elsewhere so at the end of the day it's more of an orchestration choice.