Skip to content

Auto-configure Discover from Wholphin server plugin - #2134

Merged
damontecres merged 6 commits into
mainfrom
plugin/seerr-config
Oct 26, 2026
Merged

damontecres merged 6 commits into
mainfrom
plugin/seerr-config

Conversation

@damontecres

Copy link
Copy Markdown
Owner

Description

damontecres/jellyfin-plugin-wholphin#3 added a new endpoint for Seerr configuration in Wholphin server plugin.

This PR adds support for reading that configuration and either pre-filling the URL or automatically logging in.

Some code was copied from #1418 (thanks @matschi95!), but that PR worked by inserting a DB record for the plugin provided server. Since the local DB was preferred, this meant plugin config changes wouldn't be reflected in the client. This PR instead attempts the connection and only updates the in-memory connection state, so user switching and app restarts will re-fetch from the plugin.

If the server plugin is not installed or no Seerr server is configured, nothing in Wholphin changes.

Related issues

#598

This PR replaces #1418

Testing

Emulator with different scenarios

Screenshots

N/A

AI or LLM usage

None

@damontecres damontecres added enhancement New feature or request seerr plugin labels Oct 26, 2026
@damontecres damontecres added this to the Next minor release milestone Oct 26, 2026
@damontecres
damontecres merged commit f66746c into main Oct 26, 2026
2 checks passed
@damontecres
damontecres deleted the plugin/seerr-config branch October 26, 2026 18:19
@alexkahler

Copy link
Copy Markdown

Does the plugin act as a proxy for Seer requests with this PR, is it simply getting the Seerr settings, like URL?

@voc0der

voc0der commented Oct 27, 2026 •

Copy link
Copy Markdown
Contributor

@alexkahler This might be of interest to you. damontecres/jellyfin-plugin-wholphin#7

This plugin is not currently proxying requests to Seerr. It is (currently) expected to configure seerr URL endpoints and credentials in the plugin YAML.
In short too, this PR is the app groundwork that lets you use a Seerr config which all clients will read:
(API key or local key)
https://github.com/damontecres/jellyfin-plugin-wholphin#seerr-config Upon connecting, the Wholphin clients of that Jellyfin server with the plugin, will use the configured credentials themselves.

The PR I made and linked adapts this but also uses a separate plugin to automate all of this process, and be user-specific (delegated-to-requested-user admin requests) and jellyfin-proxied. End result being turn key requestability by users.

That being said, Wholphin plugin could (and if it wants to) could devour mine if it wants ownership of that proxy code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request plugin seerr

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants