Hey all, I started hosting my own media server using jellyfin on a raspberry pi. This was mostly because I was new to the space and didn't want to invest heavily in hardware only to drop the project or find that I couldn't make it work for some reason.
I've now got it all set up and working, but the pi is absolutely not able to handle any sort of transcoding. So I'm now looking to upgrade the hardware.
Currently, I only need something that can handle transcoding two sub-4k streams concurrently. But I don't want to fully shut away the possibility of streaming 4k media. I should have the space for it, my current limiting factor is processing power.
Reading the jellyfin docs on recommended hardware, my understanding is that I should be OK if I get a recent Intel i7 CPU as long as it's got integrated graphics?
I am currently planning to build a small form factor PC and run it as a headless Linux (possibly Debian) server with jellyfin and everything else running in docker.
Mostly, I want to ask: does anyone with experience doing this have concerns or advice? In particular:
Is just the CPU processing power sufficient for everything if the CPU is chosen correctly?
If the CPU is not sufficient, is it difficult to set up a dedicated graphics card on a headless server?
Is there a place to get some of the clips they've got of Alex?
In particular, I want the "humans are born (made?) to hype?" clip to play whenever I'm tempted to upgrade my phone or whatever. I feel like the clip will snap me back to reality in a uniquely effective way
I'm just getting started on my first setup. I've got radarr, sonarr, prowlarr, jellyfin, etc running in docker and reading/writing their configs to a 4TB external drive.
I followed a guide to ensure that hardlinks would be used to save disk space.
But what happens when the current drive fills up? What is the process to scale and add more storage?
My current thought process is:
Would that work? It would mean the *arrs no longer have access to the actual downloaded files. But does that matter?
Is there an easier, better way? Some way to abstract away the fact that there will eventually be multiple drives? So I could just add on a new drive and have the setup recognize there is more space for storage without messing with volumes or app configs?
@SeaMauFive
@lemm.ee