Add a jellyfin community-container #4267
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
szaimen
added
3. to review
Signed-off-by: AiroPi <47398145+AiroPi@users.noreply.github.com> Signed-off-by: Pıεяяε <47398145+AiroPi@users.noreply.github.com>
Oops, my copy/paste is spotted Co-authored-by: Simon L. <szaimen@e.mail.de> Signed-off-by: Pıεяяε <47398145+AiroPi@users.noreply.github.com>
- Added incompatibilities between Jellyfin and Plex. - Included note about Caddy handling `media.$NC_DOMAIN`. - Added information about setting up a reverse proxy. - Included security notice for Jellyfin initial setup. Signed-off-by: Pıεяяε <47398145+AiroPi@users.noreply.github.com>
|
By the way, I was testing the Caddy config, but it seems that the Jellyfin container isn't attached to the nextcloud-aio network. Do you have any clue why? I started it using the master container web interface. |
Right. Forgot that. This is due to using the hodt network for the container... So this is something we need to figure out how to do properly... |
|
The address |
Hm, for some reason |
This is a new pull request that follows the previous one from @burnclouds, which has not been merged due to no responses. I just reused his work, with small fixes (removing a comma in the JSON).
#3634
This also follows the idea from @burnclouds: #3500
The community-container works fine, but I was wondering if I can also add some "special rules" to the Caddy community-maintained container, so it adds a jellyfin subdomain to the server with HTTPS enabled? As it is the case for Bitwarden and Stalwart.