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

Selfhosted

39245 readers
305 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
[–] [email protected] 0 points 9 months ago* (last edited 9 months ago) (1 children)

So your name resolving them over multiple networks. Seems like a headache. By exposed ports I mean the host only has the reverse proxy with a port mapping. All other conteiners have no port mapping.

[–] [email protected] 7 points 9 months ago* (last edited 9 months ago)

You can just refer to them by the name you give it in the services block, it's actually really simple. No port mappings at all.

https://nginxproxymanager.com/advanced-config/#best-practice-use-a-docker-network