Jellyfin, the open source media server, has released their 6th RC for version 10.11.0.
This is a preview release, intended for those interested in testing 10.11.0 before it’s final public release.
If you intend to test this, BE SURE you stop your Jellyfin server and take a full backup before upgrading!
WIP release notes here for now: https://notes.jellyfin.org/v10.11.0_features
See the GitHub link for more details and a full list of changes.
So when a full backup is recommended, does that include media files, or is it just the cache(?) and jellyfin database?
Backup of the jellyfin cache, Configs and database.
Your media should be outside of all that.Exactly where those things are depends on your exact install method (native/docker/Linux/windows).
https://jellyfin.org/docs/general/administration/backup-and-restore/
I hope the EFCore migration will make it easier to eventually support external databases like Postgres
There’s a PR already!
Do you have a link for that PR?
Looks like this is it: https://github.com/jellyfin/jellyfin/pull/13451 Also looks like the intention is to stabilise the new data layer before adding extra backends to avoid rework.
Thanks, Github thinking it is merged explains why I was not able to find it.
Looking forward to the release :)
I feel like something with such a major backend change that will affect compatibility deserves a higher version number. I’m going to tweak my docker compose file to ensure I dictate when this big database update happens
Be aware,
Jellyfin uses semantic versioning. All releases will have versions in the X.Y.Z format, starting from 10.0.0. Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases if required for later cleanup work
While a lot of backend changes,nothing from a user perspective wants to me jump on board…no new features and your extensions will break…I think I’ll wait lol
There should be much better performance for browsing the library
nice. Looks like they’ve made a number of significant changes. Always good to see.
This is a great update. All said, this will break my system as i have a lot of configurations.
Yeah, I’m using the OIDC plugin, so I’ll need to wait as well
According to the release notes, the DB migration could take “up to several days” depending on library size. Oof.
Hopefully no one has their DB on an HDD…
Couldn’t I just rebuild the database completely? Start from scratch and have it just remake all the metadata?
Well you would lose the watched status for all your media, as well as any custom settings and whatnot.
My plan, when the time comes to upgrade, is to copy the DB and bring up an isolated container using the copy, let the upgrade proceed in the background, then swap to the new container when the upgrade is done. That way there’s minimal downtime and no data loss.
