A homelab is your own small infrastructure at home: a spare PC, a mini server or a few single-board computers running services you choose, from file storage to DNS to a media server. It is a safe place to practise what professionals do at scale (networking, virtualization, backups, monitoring) and to find out what breaks and why.
Key concepts
- Virtualization and containers: split one machine into many isolated systems for experiments.
- Networking: static addresses, VLANs, DNS, a firewall and a reverse proxy to reach services by name.
- Infrastructure as code: describe machines and services in files, so you can rebuild them from nothing.
- Backups and monitoring: copies in more than one place, restores you have tested, metrics and alerts.
- Exposure: keep services private; if one must be reachable from the internet, put a VPN or strong authentication in front and keep it updated.
Vocabulary
- Hypervisor: software that runs virtual machines.
- NAS: network-attached storage, a box that shares files over the network.
- VLAN: a logically separate network carried over shared hardware.
- Reverse proxy: a server that receives requests and forwards each to the right internal service.
What to study, in order
- Install Linux on one machine and run a single service, such as a file share; read its logs.
- Run several services in containers or virtual machines, one per service.
- Set up DNS and a reverse proxy, so services have names instead of port numbers.
- Keep configuration in a Git repository and rebuild one machine from it.
- Add backups, then practise restoring one on a clean machine.
- Add monitoring and a VPN, and put lab and home devices on separate VLANs.
Related tags
#self-hosting #virtualization #containers #network-administration #backups