Comments

• dgdft@lemmy.world ⁨1⁩ ⁨month⁩ ago

  Is there a buried lede here? What’s noteworthy about an RC of a minor version release?

  source

  • exu@feditown.com ⁨1⁩ ⁨month⁩ ago

    This is the database rework that’s been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.

    source

    • timbuck2themoon@sh.itjust.works ⁨1⁩ ⁨month⁩ ago

      I’ll be honest, Im not sure why theyre not releasing this as 11.x.

      This seems to be a major update. From what I can tell there are API changes, plugins might not work, your entire db is converted to another format, etc.

      I’m excited for it and thankful for all the work- just seems so big that it should be tagged 11.0.0

      source

      • -> View More Comments
    • victorz@lemmy.world ⁨1⁩ ⁨month⁩ ago

      any DB access now goes through the core library

      Out of curiosity, this is better because of encapsulation? Protection from bad plugins?

      source

      • -> View More Comments
  • victorz@lemmy.world ⁨1⁩ ⁨month⁩ ago

    I’m serious, there’s so much lazy posting on Lemmy regarding software releases.

    • no mention of what the software is or does ✔️
    • no mention of what’s interesting about the software is this release. ✔️

    Jellyfin is quite a big name, but still, the pattern is clear.

    source

    • sj_zero ⁨1⁩ ⁨month⁩ ago

      I have to admit, it's something I'd like to see done a bit better (not that I'd be the one posting about it typically)

      "Crocoslut version 12 released!"

      Uh... great?

      Though sometimes you go to the website and it's not much better.

      • -> View More Comments
    • verstra@programming.dev ⁨1⁩ ⁨month⁩ ago

      We could have a tag for things like this (if tags are a thing on lemmy) or a required prefix, such as "Software release: ".

      I do like to see an announcement for things I use and have slow release schedule.

      source
  • Untold1707@lemmy.zip ⁨1⁩ ⁨month⁩ ago

    Sorry, I didn’t realize some Lemmy clients don’t show cross-post descriptions. I’ll copy past it below:

    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: 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.

    source

    • victorz@lemmy.world ⁨1⁩ ⁨month⁩ ago

      My client showed that to me and I read it. I just imagined myself as someone who doesn’t know what Jellyfin is, and that text didn’t help much.

      source
• IronKrill@lemmy.ca ⁨1⁩ ⁨month⁩ ago

  Media watch status no longer persists on media rename. When you move or rename your media files, previously Jellyfin remembered the watch status based on external IDs alone; now it uses an actual reference to the database entry. This is a transitional change and we are working on a better way to handle that in a future version.

  I hope they do figure out a solution for that soon… Until that’s fixed I’m going to stay on 10.10.7 for a while.

  source
• olafurp@lemmy.world ⁨1⁩ ⁨month⁩ ago

  Important note: This release can only be upgraded to if you’re on 10.7 or later. Make sure to update to 10.10 before it becoming more manual.

  source
• yournamehere@lemm.ee ⁨1⁩ ⁨month⁩ ago

  i gave emby and jellyfin a testrun yesterday using docker. I kept emby because i can easily add smb shares using the webinterface. jellyfin requires me to mount those to the host/container. am i using jellyfin wrong?

  source

  • gravitywell@lemmy.ml ⁨1⁩ ⁨month⁩ ago

    Why is it not mounted on the host/cointainer? I dont think you are using jellyfin “wrong” but its not like you cant just configure a mount point if you wanted to use jellyfin with it.

    That is an interesting thing to point out though, im not actually sure but i think they used to support smb shares directly, i might just be thinking of kodi though.

    source

    • yournamehere@lemm.ee ⁨1⁩ ⁨month⁩ ago

      it is not mounted to the container because that is a shit solution. the host would need to mount it and pass that to tge container. emby i stop the container and no connection to the share. mounted in host it would still be there. not to mention the hassle this also means more traffic. an idea why jellyfin doesnt do shares like emby?

      source

      • -> View More Comments
    • EncryptKeeper@lemmy.world ⁨1⁩ ⁨month⁩ ago

      Im using UnRAID for storage and getting another Linux machine to mount a share in boot has been an exercise in futility so I get it.

      source

      • -> View More Comments
  • tuxec@infosec.pub ⁨5⁩ ⁨weeks⁩ ago

    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/movies

    source

    • yournamehere@lemm.ee ⁨5⁩ ⁨weeks⁩ ago

      i 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.

      source
• iturnedintoanewt@lemmy.world ⁨1⁩ ⁨month⁩ ago

  Wow this one looks major, and possibly disruptive.

  source
• Appoxo@lemmy.dbzer0.com ⁨1⁩ ⁨month⁩ ago

  Dayum.
  Some nice things in there!

  source