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.
21 Comments
aeternum@lemmy.blahaj.zone · 16 pts · 326d
stefenauris@pawb.social · 14 pts · 326d
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
ShortN0te@lemmy.ml · 10 pts · 326d
Be aware,
mushroomman_toad@lemmy.dbzer0.com · 1 pts · 326d
Yeah, there's going to be a long, uninterruptable database migration at the next startup and they recommend taking backups before. My renovate is fully disabled for Jellyfin right now.
notfromhere@lemmy.ml · 9 pts · 326d
I hope the EFCore migration will make it easier to eventually support external databases like Postgres
mushroomman_toad@lemmy.dbzer0.com · 6 pts · 326d
There's a PR already!
domi@lemmy.secnd.me · 4 pts · 326d
Do you have a link for that PR?
Mountaineer@aussie.zone · 5 pts · 326d
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.
domi@lemmy.secnd.me · 3 pts · 325d
Thanks, Github thinking it is merged explains why I was not able to find it.
imsufferableninja@sh.itjust.works · 9 pts · 326d
According to the release notes, the DB migration could take "up to several days" depending on library size. Oof.
Chewy7324@discuss.tchncs.de · 3 pts · 326d
Hopefully no one has their DB on an HDD...
AtariDump@lemmy.world · 1 pts · 326d
Or a Pi
Auli@lemmy.ca · 1 pts · 325d
Why not mine is on an array of disks.
crazyminner@lemmy.ml · 1 pts · 315d
Couldn't I just rebuild the database completely? Start from scratch and have it just remake all the metadata?
imsufferableninja@sh.itjust.works · 2 pts · 315d
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.
timeslip1974@lemmy.world · 3 pts · 326d
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
mushroomman_toad@lemmy.dbzer0.com · 3 pts · 326d
There should be much better performance for browsing the library
firepenny@lemmy.world · 3 pts · 326d
This is a great update. All said, this will break my system as i have a lot of configurations.
faercol@lemmy.blahaj.zone · 2 pts · 326d
Yeah, I'm using the OIDC plugin, so I'll need to wait as well
Appoxo@lemmy.dbzer0.com · 3 pts · 326d
Looking forward to the release :)
HereIAm@lemmy.world · 1 pts · 325d
So when a full backup is recommended, does that include media files, or is it just the cache(?) and jellyfin database?
Mountaineer@aussie.zone · 2 pts · 325d
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/