Add JELLYSEERR_URL env var to Fladder Docker image (like BASE_URL)

[bjoernch]

Summary

I’d like to propose adding a JELLYSEERR_URL environment variable to the Fladder Docker image, implemented in the same manner as BASE_URL. This would allow users to define a fixed Jellyseerr endpoint directly in their docker-compose.yml, instead of having to manually configure it through the Fladder settings UI after deployment.

This approach would enable preconfiguration of the Jellyseerr URL at deploy time, removing the need for manual input after login. Additionally, since in most setups the same credentials are used for both Jellyfin and Jellyseerr, it would be great to offer an optional auto-configuration step: after login, the user could be prompted whether they want to reuse their Jellyfin credentials for Jellyseerr. If confirmed, the Seerr integration could be configured automatically, further streamlining the initial setup process.

Basic Example

A user deploys Fladder via Docker Compose and wants Jellyseerr to be available immediately without any manual configuration in the UI.

BASE_URL=https://jellyfin.example.com
JELLYSEERR_URL=https://requests.example.com

On login:

Fladder automatically uses https://requests.example.com as the Jellyseerr endpoint. The Jellyseerr URL field in Settings is pre-filled. The user is optionally prompted whether their Jellyfin credentials should also be used for Jellyseerr.

If confirmed, the Jellyseerr integration is configured automatically without further user input.

This allows a fully functional Jellyfin + Jellyseerr setup immediately after deployment, with no post-install configuration required via Fladder Settings.

Drawbacks

Unresolved questions

No response

Implementation

• I would like to implement this myself!

[v3DJG6GL]

Great, an ENV variable JELLYSEERR_URL is what I also had in mind :)

And I have another thought since e.g. in my case my users only have one SSO login and don't have a password to login into Jellyfin & Seerr - they use OIDC-based login for Jellyfin (https://github.com/9p4/jellyfin-plugin-sso) and Seerr (seerr-team/seerr#1505), so they don't have credentials for any of these:
Currently, Fladder has this option to set an API key to connect to Seerr:
I don't know whether normal users must have the ability to use an API key to connect to their Seerr instance. At least in my case all users can see this option.

Instead, an global ENV var SEERR_API_KEY could make all other configuration steps obsolete.
Some examples:

• The Jellyfin plugin Home Screen Sections (https://github.com/IAmParadox27/jellyfin-plugin-home-sections) does it exactly like that:
  You can set your Seerr API key there and the plugin automatically checks whether your Jellyfin account is linked to a Seerr account. If a linked account is found, you then can see your latest requests on your Home Screen.

• Similar for Jellyfin plugin Jellyfin Enhanced:
  Once linked Jellyfin<-->Seerr accounts are found, these users get the ability to make requests from within Jellyfin WebUI :)

[v3DJG6GL]

Or this could be another way to implement that functionality: seerr-team/seerr#2244
See this comment: streamyfin/jellyfin-plugin-streamyfin#82 (comment)

[PartyDonut]

Yes I saw that when I was implementing Seerr. The moment the jellyfin token can be used I will add that.
It was also the reason I'm reluctant to link the api key inside the application to all users at once. Not sure how safe that would be.

I will have a look at making both the server and api key a docker variable because it does make sense in that context.

Thanks for the suggestions 😄