Want to make a small home server/lab, get jellyfin QBittorrent and other plugins on it to have media hosted by myself, also to make my own Inviduos instance because a lot of them are being targeted right now, shifting IPs works but they still persist.
Have a rasppi4 that I used for some projects, but I think for the amount of storage that I want to put initially and then upscale would be too hard on that little thing. Plus transfer speeds. Also the processing power probably wouldn’t be great for them big movies.
Would want to get a case with the big HDD/SSD cage, some motherboard, a chip that can handle 4K processing and then RAM with expansion(albeit I will start with 8 to 16 gb), then a good power supply so I can handle the bill. So in general I’m looking at old office equipment to get stuff cheap, and efficient in electricity use.
Now to the question, I’m looking for good marketplaces in EU that have that sort of stuff. Anything will be good and if you can give several it would be even better. Thanks a lot!
Chiming in with some post-hardware-acquisition suggestions.
Read up and learn about docker and specifically docker compose. My reverse proxy of recommendation for a beginner is Nginx Proxy Manager. Debian stable server releases are great distros for your use-case.
Use least-access thought for connecting services and networks. For example only jellyfin and jellyseer needs to be on the NPM external network definition and accessible over network, not the underlying *arr stack, VPN, and torrent containers actually searching/acquiring the data.
NPM
Jellyfin
Jellyseer
Radarr
Sonarr
QBitTorrent
Containers are addressable by container name:port if they’re within the same network so you don’t need to worry about finding a container’s specific IP address. Example: when wiring up the Sonarr service’s location in the Jellyseer UI, assuming you named the Sonarr container Sonarr you can punch in Sonarr:7777 [this is just a random port for the example] and that Sonarr will resolve to the correct local IP in their shared network (arr-network in this example).
Also on the hardware side get a GPU with hardware AV1 support (the new Intel GPUs are great and cheap for this) as that’s the go-forward video codec and you’ll save tons in power on transcoding and an absurd amount of storage space over h.264 and a decent bit over h.265. It’s also worth updating clients with hardware decoding for AV1 asap so that the server has to transcode less as well (recent fire sticks and new TVs within the last 2 years should handle this already)
Also forgive me if this is all stuff you know already but also enable only key-based ssh access kinda immediately as the amount of port sniffing you’ll get on 22 is absurd.