Selfhosted

40023 readers

982 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Should I use one docker-compose.yml for all my services? (lemmy.fmhy.ml)

submitted 1 year ago by bronzing@lemmy.fmhy.ml to c/selfhosted@lemmy.world

35 comments fedilink hide all child comments

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's thread
view the rest of the comments

[–] zbecker@mastodon.zbecker.cc 0 points 1 year ago (1 children)

@midas @bronzing

Out of curiosity why not? this is what I have been doing forever.

[–] midas@ymmel.nl 2 points 1 year ago

So there's a million ways to do things and what works for you works for you. For me, putting all services ina single compose file only has downsides.

Difficult to search, I guess searching for a name and then just editing the file works - but doesn't it become a mess fairly quickly? I sometimes struggle with just a regular yaml file lmao
^also missing an overview of what you're exactly running - docker ps -a or ctop or whatever works - but with an ls -la I clearly see whats on my system
How do you update containers? I use a 'docker compose pull' to update the images which are tagged with latest.
I use volume mounts for config and data. A config dir inside the container is mounted like './config:/app/data/config' - works pretty neatly if each compose file is in its own named directory
Turning services on/off is just going into the directory and saying docker compose up -d / or down - in a huge compose file don't you have to comment the service out or something?