One weekend Project
Your first self-hosting weekend, step by step
This is the project we wish someone had handed us at the start: one small machine, two days and an order of work that ends with three services the household actually uses, reachable from anywhere and backed up. No hypervisor, no rack, no shopping list longer than a page.
- BeginnerDifficulty
- 2 daysTime, with breaks
- 1 machine16 GB memory, SSD, wired
- $0 to $250Typical cost
What you will build
By Sunday evening you will have a small Linux server running three services in containers: an uptime monitor, a password vault and either a photo library or a media server. Each will have a proper name and certificate, you will be able to reach them from your phone away from home, and you will have restored a backup to prove it works.
We deliberately use plain server Linux with a container engine rather than a hypervisor. One layer means your energy goes into learning containers instead of fighting the platform. You can move to a hypervisor later; see Choosing a Platform for the trade-offs.
Before the weekend
- Pick your three services. Write down which subscription or annoyance each one replaces. For most households: an uptime monitor first, a password vault second, then whichever of a photo library or media server would be missed most. Not both.
- Prepare one always-on machine with at least 16 GB of memory, an SSD and a wired network connection. A refurbished business mini PC is ideal; a spare desktop works too. See Budgeting a Homelab.
- Have a second computer to work from, a USB stick for the installer and an external drive for backups.
- Know your domain plan. If you own a domain, you can use names such as photos.lab.example.net with real certificates. See DNS, Domains and Certificates.
Saturday morning: a server you can reach
- Write the installer. Download a long-term support server distribution from its official site and write it to the USB stick with a trusted imaging tool. Check the target device twice; choosing the wrong one erases it.
- Install minimally. Choose the minimal server profile, create your own user, and enable the SSH server when the installer offers it. Skip every optional extra.
- Fix the address. Create a DHCP reservation on your firewall or router so the server always gets the same address. In our example network it becomes apps01.lab.example.net at 10.42.30.30 on the lab VLAN. Write it in your notes.
- Work over SSH. From your second computer, connect over SSH and treat that as your workstation from now on. You will rarely need the server's screen again.
- Update and harden. Install updates, set the time zone, enable automatic security updates, install your SSH key and turn off password logins. The details are in Linux for the Homelab.
Saturday afternoon: containers
- Install the container engine from your distribution's repository or the project's official package repository. Some guides offer a one-line convenience script piped into a shell; if you use one, read it first, because it runs as root.
- Allow your user to manage containers. Add your user to the engine's group, then log out and back in, or the change will not apply. Understand that this group is effectively root on the machine.
- Test it by running a tiny test image and confirming it prints its greeting.
- Learn compose files. Spend twenty minutes on this before deploying anything real. Create one directory per service under /srv, each holding a compose file and its data. A service described in a file can be stopped, deleted and recreated identically in seconds.
- Deploy the uptime monitor first. It takes minutes and pays off immediately. Add checks for your firewall, your provider's gateway and a public DNS resolver. From now on, it tells you the moment anything else breaks, including the services you are about to add.
From the Bench
Every one of us has watched a first container refuse to start for a reason that made no sense. Nine times out of ten the logs say exactly why: a port already in use, a typo in a path or a data directory the container cannot write to. Read the container's logs before searching the web.
Sunday morning: names, certificates and the vault
- Add a reverse proxy. Run a reverse proxy container that listens on ports 80 and 443 and forwards each name to the right service. Every other container publishes its port only on localhost.
- Create internal names. Add DNS records on your local resolver, usually the firewall or router, so names such as status.lab.example.net and vault.lab.example.net point at 10.42.30.30.
- Get a certificate. Issue a wildcard certificate for *.lab.example.net using DNS validation, so nothing has to be reachable from the internet. If it fails at first, the usual cause is a DNS record that has not propagated or an answer cached somewhere; wait and retry.
- Deploy the password vault. Password vaults expect HTTPS, which is why they come after the proxy. Create your account, import from your old manager, and install the official client apps on your devices.
Sunday afternoon: the third service, remote access and a backup
- Deploy your third service, the photo library or the media server. Point its large data directory at a disk with room to grow, and note the path.
- Set up remote access with a mesh VPN rather than opening ports. Our Mesh VPN Remote Access project covers it step by step.
- Back up /srv and the large data directory. Schedule a nightly job that dumps each database, then copies /srv and the photo library's or media server's data directory to the external drive with versioning. Have it check in with your uptime monitor when it succeeds.
- Restore something now. Restore the vault's data directory and a handful of photos to a scratch location and open them. Your first restore test will very likely reveal that you backed up the wrong directory, or missed one. Far better to find out today.
- Write it down. Record each service, its address, where its data lives and how it is backed up. See Maintenance Routine for a simple service catalog format.
What usually goes wrong
| Symptom | Usual cause |
|---|---|
| Permission denied running container commands | You have not logged out and back in after joining the group |
| Container exits immediately | Port conflict, wrong path or a data directory it cannot write to; read its logs |
| Name does not resolve | The record is missing on the firewall's resolver, or the client is using a different DNS server |
| Certificate request fails | DNS record not yet visible, or an API token with too few permissions |
| Data gone after recreating a container | The data was written inside the container instead of a mounted directory |
Verify
- Every service opens by name with a valid certificate, at home and from your phone on mobile data.
- The uptime monitor shows all three services and alerts you when you stop one deliberately.
- Rebooting the server brings every service back without you touching anything.
- Last night's backup exists, and you have opened files restored from it.
Next weekend
- A start page that lists every service, so nobody bookmarks addresses again.
- An off-site copy of the vault and photos. See Backup Strategy.
- Single sign-on, once you run four or five services with separate logins.
- A deliberate update routine rather than automatic image updates. See Maintenance Routine.
- A hypervisor, when you want virtual machines. See Mini PC Hypervisor Build.
The difference between people who still have a homelab a year from now and people who do not is rarely skill. It is that the first group got three services working properly before adding a fourth.