Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on aussie.zone
jellyfin·Jellyfin: The Free Software Media SystembyMountaineer

Jellyfin 10.11.0 RC6

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.

Jellyfin 10.11.0 RC6https://github.com/jellyfin/jellyfin/releases/tag/v10.11.0-rc6Open linkView original on aussie.zone
119

21 replies

pawb.social

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

14

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

10

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.

1
lemmy.ml

I hope the EFCore migration will make it easier to eventually support external databases like Postgres

9

Thanks, Github thinking it is merged explains why I was not able to find it.

3

According to the release notes, the DB migration could take "up to several days" depending on library size. Oof.

9
Aulireply

Why not mine is on an array of disks.

1
Norareply
lemmy.ml

Couldn't I just rebuild the database completely? Start from scratch and have it just remake all the metadata?

1

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.

2
lemmy.world

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

3
lemmy.world

This is a great update. All said, this will break my system as i have a lot of configurations.

3
lemmy.world

So when a full backup is recommended, does that include media files, or is it just the cache(?) and jellyfin database?

1

You reached the end

Jellyfin 10.11.0 RC6 | Spyke