meh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 13 hours agogoodbye plexpiefed.cdn.blahaj.zoneimagemessage-square122fedilinkarrow-up1502arrow-down120file-text
arrow-up1482arrow-down1imagegoodbye plexpiefed.cdn.blahaj.zonemeh@piefed.blahaj.zone to Selfhosted@lemmy.worldEnglish · 13 hours agomessage-square122fedilinkfile-text
after almost 15yrs my plex server is no more. jellyfin behind nginx with authentik is running very nicely.
minus-squaredaniskarma@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up42arrow-down2·edit-29 hours agoI’ve been using jellyfin for years. My best recommendation is DELAY UPDATES and back up before you update. I have a history of updates breaking everything so you should be careful about them. All software recommends backing up before an update, but for jellyfin the shit is real, you really want to back up.
minus-squareLem453@lemmy.calinkfedilinkEnglisharrow-up9·edit-23 hours agoI’ve been using jelly since just after the emby fork and never had an update issue on docker. Automatic snapshots every 5 mins (amoung other backup tools). means I don’t need to worry much if it does.
minus-squareSupremeDonut@lemmy.mllinkfedilinkEnglisharrow-up1·6 hours agoLike the version or the media?
minus-squaredaniskarma@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up3·6 hours 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-up5·3 hours agoWith respect to the media, you can mount the volume as read only, preventing Jellyfin from accidentally wiping your underlying content.
minus-squareWhyJiffie@sh.itjust.workslinkfedilinkEnglisharrow-up1·5 hours 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
minus-squareyeehaw@lemmy.calinkfedilinkEnglisharrow-up11arrow-down18·9 hours agoJellyfin still so buggy though. The UI is garbage too. I want to love it… I run both lol.
I’ve been using jellyfin for years.
My best recommendation is DELAY UPDATES and back up before you update.
I have a history of updates breaking everything so you should be careful about them.
All software recommends backing up before an update, but for jellyfin the shit is real, you really want to back up.
laughs in immich
I’ve been using jelly since just after the emby fork and never had an update issue on docker. Automatic snapshots every 5 mins (amoung other backup tools). means I don’t need to worry much if it does.
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.
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
Jellyfin still so buggy though. The UI is garbage too. I want to love it… I run both lol.