meh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 22 days agogoodbye plexpiefed.cdn.blahaj.zone18480931
778goodbye plexpiefed.cdn.blahaj.zonemeh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 22 days ago184
after almost 15yrs my plex server is no more. jellyfin behind nginx with authentik is running very nicely.
Show Contentdaniskarma@lemmy.dbzer0.comEnglish6·21 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.
Show Contentbradbeattie@lemmy.caEnglish10·21 days agoWith respect to the media, you can mount the volume as read only, preventing Jellyfin from accidentally wiping your underlying content.
Show ContentAllHailTheSheep@sh.itjust.worksEnglish1·21 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.
Show ContentWhyJiffie@sh.itjust.worksEnglish2·21 days agothe config and databases or the media, you mean? if so, the former, but I mount the meadia with a read only docker volume just to be sure, because chances are I would never notice it
Like the version or the media?
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.
the config and databases or the media, you mean?
if so, the former, but I mount the meadia with a read only docker volume just to be sure, because chances are I would never notice it