Yeah you definitely want each ‘thing’ in its own compose file. Take a look at Portainer or Dockge to easily manage multiple compose files.
Comment on My Overconfidence Killed Me and My Immich Installation
sabreW4K3@lazysoci.al 7 months agoThanks for the info. In my head, I had one eye on the future, because honestly, when I chuck it in the corner, I know myself, I won’t be arsed enough to jump from directory to directory to run the individual compose files and so I’m kinda aiming to have everything run from a single docker compose. Am I being naive?
MangoPenguin@lemmy.blahaj.zone 7 months ago
avidamoeba@lemmy.ca 7 months ago
Definitely don’t put everything in a single docker-compose file. For one compose files change from the developer to add/adjust things. You want to make updating to the latest one as easy as copying it over the existing one with minor changes if any, ideally none. For another, you shouldn’t rely on running any of it manually. If you want to chuck it in a corner, write some systems unit files to start and restart the docker compose services for you. Finally, it’s not too difficult to find what compose files you have once you’ve forgotten them. Use
docker compose ls, plaindockerand if all else failsfind,grep.sabreW4K3@lazysoci.al 7 months ago
I love this community. Thank you so much.