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

Selfhosted

40749 readers
448 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 2 years 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
[–] eager_eagle@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (1 children)

if these are the only services one is self hosting, I can see that.

But I have around a dozen stacks atm and I never came across a situation that I wanted to trigger an *arr stack restart with Jellyfin's. They're pretty much unrelated and independent services from an operational view.

[–] Kusimulkku@lemm.ee 1 points 1 year ago

You can issue commands to singular services or group them under an alies if needed.

But I have around a dozen stacks atm and I never came across a situation that I wanted to trigger an *arr stack restart with Jellyfin's. They're pretty much unrelated and independent services from an operational view.

I'm more talking about pull, up -d. It's convenient having it all behind a single command, unless there's a special need to have them separated