all-in-one
all-in-one copied to clipboard
Add a jellyfin community-container
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).
https://github.com/nextcloud/all-in-one/pull/3634
This also follows the idea from @burnclouds: https://github.com/nextcloud/all-in-one/discussions/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.
Alright, I will check for the DCO issue 👍
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.
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 host.docker.internal
can be used for the reverse-proxy, but I don't know how to check if jellyfin is installed and present.
The address
host.docker.internal
can be used for the reverse-proxy, but I don't know how to check if jellyfin is installed and present.
Hm, for some reason host.docker.internal
isn't accessible from the caddy container