• 1 Post
  • 77 Comments
Joined 4 months ago
cake
Cake day: August 22nd, 2024

help-circle




  • Honestly a raspberry pi or equivalent on diet pi (https://dietpi.com/) is probably a good start. Though with the caveat that you should use its internal utilities to create an off-site backup of your most important data via a provider such as hetzner.

    Cheap, low power, and diet pi is Debian with some tweaks so it’s very easy to set up either bare metal or via containers (as others have said containers may help manage things easier and safer in the long run).

    For storage, you’ll probably either need an externally powered USB dock (30ish EUR) or a powered 3.5inch HDD dock if you go this route as the pi cannot reliably power even one SSD from its USB ports - you’ll risk IO failures. The same will come from any setup that includes any low power SBC just for stability. In my experience it’s still less than 15W but you need stable power for IO stuff on SSDs.





  • web Devs aren’t ignorant to optimizing but the kind of interfaces used in web are very different to that of desktop. Cross platform technologies can work, but anything built on top of web engines is going to be a little dogshit on native platforms.

    Web tech was designed around the asynchronous and comparatively slow nature of the network. Now, those same layout and rendering engines are being shoehorned into an environment where the “server” is your local disk so it’s suddenly doing a bunch of work that was intended to be done iteratively.

    Same goes the other way of course. Software designed for “native first” experiences like Flutter aren’t as popular in web dev because they work on that same, but reversed, assumption of a local disk being your source.

    It would be like wondering why physical game disks aren’t popular on PC - it’s a fundamentally different technology for fundamentally different expectations and needs.










  • Depends on your experience, hardware, and other stuff.

    You could easily use Debian or Ubuntu server and install Docker if all you want is those listed services installed on unRAIDed drives.

    You could try something like Dietpi (which is what Ive used since I started self hosting) which simplifies a few things and gives some helpful scripts on top of a basic Debian installation. It’s a simple setup but still just plain ol’ Debian so easy to set up however you like.

    You could use something like CasaOS or ZimaOS which offer Web interfaces and integrate with docker for those with a “no tech” background up to technical users.

    ProxMox is an option, but takes a lot of learning proxmox-specific stuff and IMO might be a bit overkill for your first server.

    Personally, I’d go for something accessible to your tastes because everything nowadays has some kind of “easy setup” path for Plex/Jelly + Arr. Once it’s set up, use it! Then once you need a big change for better hardware or more bespoke software setups then start digging into more fancy setups.