- cross-posted to:
- jellyfin@lemmy.ml
- cross-posted to:
- jellyfin@lemmy.ml
cross-posted from: https://lemmy.zip/post/40833329
We are pleased to announce the first release candidate preview release of Jellyfin 10.11.0!
This is a preview release, intended for those interested in testing 10.11.0 before it’s final public release. We welcome testers to help find as many bugs as we can before the final release.
As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!
WIP release notes: https://notes.jellyfin.org/v10.11.0_features
This is the first release that uses the new EF Core database mapper. If you’d like to help test this release, please remember to remove all plugins to make debugging logs as easy as possible.
I see you’ve got some downvotes, but without anyone suggesting a solution.
You can add the mount points in the docker compose file and then configure Jellyfin to read from the path(s) mounted in the container (/media/movies)
Eg:
volumes: # local path : path in container - /mnt/storage/media/movies:/media/moviesi know. i did. i hate it. thanks though. but that usually also requires fiddling with fstab and nobody wants that. just imagine the user roles and rights desasters that anyone with access to the host can see the mount. mount where you need the data, not in 2 or more places just to access it from one place. for me personally emby works much better on this. there are so many environments where you can deploy docker but not modify the host - so i do not see jellyfin really being useable here. i wish they’d add this, but from google searches i understand that it has been requested and there does not seem to be any intention to implement it.