Add artifactapi remotes for jellyfin-ha auth plugins #39
Reference in New Issue
Block a user
Delete Branch "benvin/jellyfin-plugin-remotes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
jellyfin-ha bakes the LDAP and SSO authentication plugins into its image at build time. Per policy, all outside artifacts must be fetched through artifactapi rather than pulled directly from upstream.
How
config/remote_generic/jellyfin.yaml, a new generic remote proxyinghttps://repo.jellyfin.org, scoped (least-privilege) to the ldap-authentication plugin zip.config/remote_generic/github.yamlremote for9p4/jellyfin-plugin-ssorelease zips. GitHub redirects release downloads toobjects.githubusercontent.com; the existing github remote already follows those redirects (it proxies many other release assets the same way).Proxied URLs the Dockerfile will use afterwards
http://artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/jellyfin/files/plugin/ldap-authentication/ldap-authentication_22.0.0.0.ziphttp://artifactapi.k8s.syd1.au.unkin.net/api/v1/remote/github/9p4/jellyfin-plugin-sso/releases/download/v4.0.0.4/sso-authentication_4.0.0.4.zipValidation
yamllint(relaxed, repo pre-commit config) passes on both changed files.