Release 12.0 · jellyfin/jellyfin
github.com
🚀 Release notes for 12.0 Notes on Updating Before upgrading from an earlier version, a full backup of the data directory is strongly recommended, as this release includes database changes that prev...

Why jump from 10.11.11 directly to 12.0? -> Blog Post

You can find more details about and discuss this release on the official forums.

As always, please ensure you stop your Jellyfin server and take a full backup of your metadata/configs before upgrading!

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

___

  • Klox@lemmy.worldEnglish
    19·
    2 days ago

    What a banger release! Super excited for the future. I know some folks were worried about the change in leadership, but this is super promising. Heres hoping runway is clear for Postgres at some point.

      • Klox@lemmy.worldEnglish
        3·
        1 day ago

        Why what? Why do I want Postgres? Because my database is on an iSCSI partition that is brittle.

        • iamthetot@piefed.caEnglish
          2·
          1 day ago

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

          • Klox@lemmy.worldEnglish
            5·
            1 day 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.