My Homelab Setup
This post details a homelab setup, repurposing an old gaming PC for data storage, backup, and self-hosting various applications, including local LLMs. It particularly highlights using TrueNAS and Tailscale for robust, private infrastructure. The Hacker News community appreciated the practical, detailed guide while sparking lively debate on homelab definitions and technical implementations.
The Lowdown
Facing a data backup dilemma and rising hard drive prices fueled by AI, the author decided to build a homelab using a repurposed gaming PC. This setup provides a robust solution for storing Fujifilm RAW files and exploring self-hosted applications, embracing a self-sufficiency ethos.
- Hardware Foundation: An AMD Ryzen 5 2600X, GTX 1070 Ti, 16GB RAM, and a mix of SSDs/NVMe are combined with two 8TB Western Digital Red Plus HDDs configured in RAID 1 for data redundancy.
- Operating System: TrueNAS Community Edition serves as the backbone, offering network-attached storage capabilities and critical features like ZFS snapshots for data protection.
- Self-Hosted Applications: The lab hosts a diverse array of apps: Scrutiny for drive health monitoring, Backrest (a web frontend for Restic) for backups to Backblaze B2, Immich for photo/video management, Mealie for recipe organization, and Ollama for running local large language models.
- Remote Access: Tailscale provides secure, public internet-free access to the homelab and its services from anywhere, simplifying remote management.
- Future Enhancements: The author plans to implement custom domain names and a reverse proxy to improve service accessibility and password manager integration.
This homelab represents a practical approach to personal data management and digital autonomy, demonstrating how readily available hardware can be transformed into a powerful self-hosting platform.
The Gossip
Homelab Hashing It Out
A significant portion of the comments delved into defining what constitutes a 'homelab,' with some users suggesting the author's setup was 'extremely light' or not a 'proper homelab.' This sparked a debate against gatekeeping, arguing that any personal setup for learning and self-hosting, regardless of complexity, qualifies. The consensus leaned towards embracing diverse setups, recognizing that everyone starts somewhere.
Networking Nuances
The author's desire for custom domain names for self-hosted apps ignited a discussion on networking solutions. Commenters provided extensive advice on implementing reverse proxies like Nginx, Caddy, or Traefik, often combined with local DNS services (AdGuard Home, Pi-hole) for internal routing. Cloudflare Tunnels and advanced Tailscale features (like Tailscale Services) were also suggested for simplified, secure access and certificate management.
Backup & Build Battles
Backup strategies and hardware philosophy were hot topics. Many users chimed in with their preferred off-site backup destinations, including Hetzner StorageBox as an alternative to Backblaze B2. A provocative discussion emerged about using a friend's house for off-prem backups rather than corporate cloud providers. There were also warnings about the lack of ECC memory for long-term storage and debates on consolidating services on one machine versus splitting them across dedicated hardware (e.g., NAS as just a NAS).
Performance & Power Ponderings
Several commenters discussed the power consumption of the author's setup, suggesting that repurposing an old gaming PC might not be the most energy-efficient choice compared to dedicated low-power machines or mini-PCs. This led to a broader conversation about hardware sizing for homelabs, with many asserting that the mentioned services, even with multiple game servers, are surprisingly light on resources and can run on much less powerful (and more power-efficient) hardware like Raspberry Pis or older i7s.