I’m pretty new to self-hosting in general, so I’m sorry if I’m not using correct terminology or if this is a dumb question.

I did a big archival project last year, and ripped all 700 or so DVDs/Blu-rays I own. Ngl, I had originally planned on just having them all in a big media folder and picking out whatever I wanted to watch that way. Fortunately, I discovered Jellyfin, and went with that instead.

So I bought a mini pc to run Ubuntu server on, and I just installed Jellyfin directly there. Eventually I decided to try hosting a few other services (like Home Assistant and BookLore (R.I.P.)), which I did through Docker.

So I’m wondering, should I be running Jellyfin through Docker as well? Are there advantages to running Jellyfin through Docker as opposed to installed directly on the server? Would transitioning my Jellyfin instance to Docker be a complicated process (bearing in mind that I’m new and dumb)?

Thanks for any assistance.

  • Carrot@lemmy.todayEnglish
    5·
    1 day ago

    Don’t change now if you don’t have an issues in my opinion. However, if you have the space for the jellyfin backup, it should be a pretty simple transition. I always prefer deploying using docker compose for all my services, I have backups of the compose files, and it handles all the networking between all the services (VPN, *arr stack, qbt, seer, jellyfin) When I had to move off of my ancient server after it kicked the bucket, it was as simple as copying my compose files, a single docker deployment per stack, and loading the backups for specific services. I’ve not had any issues with Jellyfin on docker, but I am using GPU passthrough to allow for hardware accelerated transcoding.