Skip Navigation

What is the most efficient method to set up a home server?

Hey guys, I'm new to self-hosting; I'm trying to set up cloud storage to store pics and other content. However, I’m unsure whether to use my old computer, Buy NAS or ResberryPie to set up a home server.

Also, what is the best privacy-friendly OS to use with the home server?

Lastly, do’s and don’ts.

Any help would be appreciated (:

76 comments
  • Use docker compose . Like "everyone" uses it. If the service doesn't have a compose file, request it, or write it yourself as son as you are knowledgable enough.

    Use podman as soon as people and services switch to it (you'll know when the latest tutorials talk about podman instead of docker).

    Use ngingx proxy manager or another easy to use reverse proxy.

    Don't think it's production ready after it was working 2 days. It may be, but it's unlikely you have enough knowledge how to fix things.

    Automatic updates.

    Don't install crap on the system.

    • This is a good way to get started.

      Docker and Docker compose on whatever hardware you want to start on.

      Don’t think it’s production ready after it was working 2 days. It may be, but it’s unlikely you have enough knowledge how to fix things.

      Most important there. You aren't building a production system for corporate clients, you're doing this for fun. Focus on one thing, try to get that one thing running. Toy with it, make it work. Then start on your next thing. Slowly you'll build up a large system, but it won't be immediate.

      I personally have been working on switching from compose to kubernetes, which is way more advanced than a starter needs - but I've been slowly migrating for about 4 weeks now, one service at a time. Just how homelabs are done

  • If you want something that works without you fretting with the base system too much, and gives you a decent GUI to handle the base: Proxmox. Run VMs, run containers on said VMs, and experiment as much as you would like.

    I will personally not be doing this (I plan to run Alpine as my base instead of Debian, even though I hold the latter in very high regard), automate provisioning with Ansible, and exclusively use Podman instead of Docker. I'm willing to go through the pains of not using Docker directly, but at least I'm not learning how to run everything on k8s (which is not a bad idea at all, but for most homelabs without HA, it's overkill).

    Learn networking, learn container orchestration, learn GNU/Linux (or in my case, non-GNU/Linux - yes you plebs, musl is good) security, auth basics, UNIX permissions, general automation, and give yourself time.

    Also, do not become the family system-admin without having a fair bit of experience doing this already. You don't want the homelab becoming a job, which means getting to fix it at your own schedule, not when Jellyfin is broken and Wifey is bearing down on you because you cancelled Netflix in favour of your Linux ISO-powered library.

  • Go for a used small form factor PC. They usually have a decent amount of house power and can house many drives

  • Try the pi for tinkering since it will be cheaper. If you end seeing issues with performance for the usage you need you could start looking up used laptops or optiplexes.

    I had some used componentes lying around so I frankesteined a server with used parts after buying some disks

76 comments