this post was submitted on 01 Dec 2023
38 points (95.2% liked)

Selfhosted

40329 readers
316 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
 

I followed trash guides to set everything up blindly and my set up is working well. But, I feel like having jellyfin in the same docker compose as my "arr" services isn't good. So, I'd be curious to see if I should split things up. I am even wondering if i should let portainer manage everything.

you are viewing a single comment's thread
view the rest of the comments
[–] CalicoJack@lemmy.dbzer0.com 4 points 11 months ago* (last edited 11 months ago) (1 children)

You can interact with a single container if you need to, not just the whole compose group. docker compose restart jellyfin works for your example, and "restart" can be swapped for stop or start as needed.

Splitting compose files can be a good idea, but it isn't always necessary.

[–] eager_eagle@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

yes, but I use one alias for all stacks to down, pull, up as a daemon, and watch its logs.

So I'd rather split the stack than have a special treatment for it.