I’ve never done any sort of home networking or self-hosting of any kind but thanks to Jellyfin and Mastodon I’ve become interested in the idea. As I understand it, physical servers (“bare metal” correct?) are PCs intended for data storing and hosting services instead of being used as a daily driver like my desktop. From my (admittedly) limited research, dedicated servers are a bit expensive. However, it seems that you can convert an old PC and even laptop into a server (examples here and here). But should I use that or are there dedicated servers at “affordable” price points. Since is this is first experience with self-hosting, which would be a better route to take?

  • chingaderaEnglish
    2•5 days ago

    I bought a used m920q for this reason, still working on it, I’m at the docker-compose phase

    • @pezhore@infosec.pubEnglish
      2•5 days ago

      Those are beasts! My homelab has three of them in a Proxmox cluster. I love that for not a ton of extra money you can throw in a PCIe expansion slot and the power consumption for all three is less than my second hand Dell Tower server.

      • chingaderaEnglish
        1•5 days ago

        Do you have any good resources I can look at to see if a cluster is something I should look into?

        • @pezhore@infosec.pubEnglish
          1•15 hours ago

          Not really, but I can give you my reasons for doing so. Know that you’ll need some shared storage (NFS, CIFS, etc) to take full advantage of the cluster.

          1. Zero downtime for patching. Taking systems offline to update Proxmox sucks, especially if the upgrade fails for some reason. A cluster means I can evacuate one host, upgrade it, and move on to the next with no downtime for the hosted VMs.
          2. Critical service resiliency. I have a couple of critical systems in my home lab that, if they unexpectedly go down, will make for a very bad day. For instance, my entire home network (and lab) is configured to use a PowerDNS cluster for DNS. I can put the master PowerDNS server on one host and the slave on a second host - if I have a hardware failure, I won’t lose DNS. I have a similar setup for my Kubernetes cluster’s worker nodes.
          3. Experimentation. A cluster gives me a larger shared pool of CPU/Memory than my single host could offer. This means I can spin up new VMs, LXC containers, etc and just play with new software and services. Heck that’s how I got started with my Kubernetes cluster - I had some spare capacity so I found a blog post that talked about Kubes on LXC containers and I spun it up.

          I hope that helps give some reasons for doing a cluster, and apologies for not replying immediately. I’m happy to share more about my homelab/answer other questions about my setup.

          • chingaderaEnglish
            1•13 hours ago

            That makes sense, thanks for sending that. My needs are far less critical or have a need to redundancy like that but just knowing that is an option is awesome