cross-posted from: https://aussie.zone/post/36389875

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

___

  • German The Jackal@pawb.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    18 hours ago

    See, that’s a problem for me, because Plex uses anywhere between 20 and 200MB depending on what it’s doing. Mostly it idles at 50MB which keeps me very happy. When I tried Jellyfin fairly recently, it ate 1.4GB just to initialize and then promptly crashed my system. I don’t like to dunk on languages like that, but Python man… I don’t have that kind of luxury. It’s not just “cache” either, I wasn’t able to configure JF in any way where it wouldn’t crash, it’s certainly not “reclaimable” memory usage, it’s just a chunky program.

    I never even got to transcoding, it’s impressive, honestly, how fast it destroyed my homelab lol.