Jellyseerr Community Container

[Anvil5465]

It would be nice to have a Jellyseerr community container for more easily managing Jellyfin/Plex content. Support for jellyseerr could be added to the caddy community container as well for WAN access.

[szaimen]

Hi, good idea! the community container feature could be used for that. See this doc how to add a container to the list. PRs are welcome!

[szaimen]

I also added this to the list in #5251

[Anvil5465]

Started a PR at #5911

[szaimen]

Thanks! :)

[AlexandruNegura]

I saw this has been added recently. Can someone explain how one can use this? And what does it have to do with Nextcloud?

[AlexandruNegura]

I read about the community containers. So it makes the jellyseer available on local network. And if you want it can also make it available under jellyseer.$NC_DOMAIN. Is there an advantage of using this? I don't quite understand why one would want this.

[Anvil5465]

It's forked from overseerr which you can read more about here: https://overseerr.dev/

Basically it creates a simple interface for discovering and requesting new content for jellyfin.

It's not directly related to nextcloud, but I use nextcloud, jellyfin, and jellyseerr with reverse proxy so I figured why not just package jellyseerr with AIO so others can benefit as well.

[AlexandruNegura]

Thanks, I already know what *fin *seer apps are. I myself am using plex & overseer. What I wanted to ask what is the benefit of packaging this with Nextcloud?

Just ease of install & ease of configuration?

[Anvil5465]

Just ease of install & ease of configuration?

Yup

You could also argue ease of data management since nextcloud provides a nice interface to rename folders, remove/add files, etc.