meh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 2 个月前goodbye plexpiefed.cdn.blahaj.zoneimagemessage-square183linkfedilinkarrow-up1805file-text
arrow-up1805imagegoodbye plexpiefed.cdn.blahaj.zonemeh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 2 个月前message-square183linkfedilinkfile-text
after almost 15yrs my plex server is no more. jellyfin behind nginx with authentik is running very nicely.
minus-squaredaniskarma@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up6·2 个月前I have it on docker with two volumes, ./config and ./cache I back up those before each update. A bad Jellyfin update should not mess with your media folder in anyway. Though you should have backups of those aswell as a rule of thumb.
minus-squarebradbeattie@lemmy.calinkfedilinkEnglisharrow-up10·2 个月前With respect to the media, you can mount the volume as read only, preventing Jellyfin from accidentally wiping your underlying content.
minus-squareAllHailTheSheep@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 个月前or just change the folder ownership to whatever user you use in the container, but don’t give them write access. that’s how I do it so I can still edit my media as root.
I have it on docker with two volumes, ./config and ./cache
I back up those before each update.
A bad Jellyfin update should not mess with your media folder in anyway. Though you should have backups of those aswell as a rule of thumb.
With respect to the media, you can mount the volume as read only, preventing Jellyfin from accidentally wiping your underlying content.
or just change the folder ownership to whatever user you use in the container, but don’t give them write access. that’s how I do it so I can still edit my media as root.