this post was submitted on 09 Jul 2023
58 points (100.0% liked)

Selfhosted

39948 readers
613 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
58
Should I use one docker-compose.yml for all my services? (lemmy.fmhy.ml)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
38 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
[–] [email protected] 37 points 1 year ago (7 children)

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.

[–] [email protected] 6 points 1 year ago

This is exactly what I do and could not be happier!

[–] [email protected] 6 points 1 year ago

In case anyone cares here is my script, I use this for backups or shutting down the server.

#!/bin/bash

logger "Stopping Docker compose services"

services=(/home/user/docker/*)    # This creates an array of the full paths to all subdirs
#the last entry in this array is always blank line, hence the minus 1 in the for loop count below

for ((i=0; i<=(${#services[@]}-1); i++))
do
    docker compose -f ${services[i]}/docker-compose.yml down &
done

#wait for all the background commands to finish
wait
[–] [email protected] 4 points 1 year ago

Exactly my setup and for exactly the reasons you mentioned

[–] [email protected] 2 points 1 year ago (1 children)

Exactly what I do except my master folder is ~

[–] [email protected] 2 points 1 year ago

I do ~/docker so I also have a docker-prototype folder for my sandbox/messing around with non-production stuff and I have a third folder for retired docker services so I keep the recipe and data in case I go back.

[–] [email protected] 1 points 1 year ago

@czardestructo I like the tidiness of this.

[–] [email protected] 1 points 1 year ago (1 children)

Does portainer just work?

[–] [email protected] 1 points 1 year ago

To answer my own question, yes, yes it does. Should've done this ages ago...