meh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 28 days agogoodbye plexpiefed.cdn.blahaj.zoneimagemessage-square183fedilinkarrow-up1804arrow-down130file-text
arrow-up1774arrow-down1imagegoodbye plexpiefed.cdn.blahaj.zonemeh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 28 days agomessage-square183fedilinkfile-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·28 days agoI 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·28 days agoWith 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·27 days agoor 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.