Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0.

Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing.

Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back.

Go to Dashboard -> Plugins -> Manage Repositories
Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json

After migrating please perform the following steps.

Perform a full library scan to restore alternative versions
Run the "Optimize database" scheduled task

___

you are viewing a single comment's thread
view the rest of the comments

[–] iamthetot@piefed.ca 2 points 2 days ago (1 children)

Your answer only opened more questions for me so I'm going to conclude this is above my head lol.

[–] Klox@lemmy.world 5 points 2 days ago

I'm happy to provide more details if you're interested/have specific questions.

I'm running the Jellyfin app on my home kubernetes cluster -- Kubernetes (k8s) boils down to a program scheduler with a lot of big features a lot of IT folks like. K8s runs the Jellyfin program as a "pod", and it attaches remote storage to the pod. The storage is your videos/media, but also the Jellyfin database (as a sqlite file).

There are better, more reliable ways to provide a database to an app though. Jellyfin + the sqlite database is basically just a file and that file doesn't exactly play nice when it is stored remotely. Instead, the app could use a software interface (API) that allows many kinds of databases -- sqlite OR a dedicated database service (e.g. Postgres), and there are a lot of advantages to that.