Selfhosted

39226 readers

483 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:

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

Do you configure your servarr docker containers from one docker-compose file, or individual ones? (lemmy.world)

submitted 9 months ago by AbsurdityAccelerator@lemmy.world to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

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

[–] ecliptik@lemmy.ecliptik.com 3 points 9 months ago

Single hand-crafted artisan organic GMO-free compose file for services that egress through regional VPNs and are exposed internally through Tailscale; *arr, transmisson, piped, etc.

Plex, iSponsorBlock, ArchiveBox have their own compose files since I keep them close to upstream. This way when the inevitable breaks they're easier to troubleshoot.