Nobara Homelab Basics
Setting up a Fedora-based homelab on Nobara — services, networking, and why Linux matters for agent development.
- nobara
- homelab
- linux
Why Nobara
Nobara gives you a gaming-ready Fedora base with sensible defaults. For a developer homelab, that means fewer driver headaches and a rolling-ish experience without abandoning stability entirely.
Core services
My homelab runs a minimal but useful stack:
- Docker / Podman — containerized dev dependencies
- Caddy — reverse proxy with automatic HTTPS for local
.homedomains - Tailscale — secure remote access without exposing ports
- n8n — self-hosted workflow automation
Network layout
Internet → Router → Homelab host (Nobara)
├── Caddy (443)
├── n8n (5678)
└── Dev VMs / containers
Agent development angle
Running agents against local services (Ollama, custom MCP servers, webhook endpoints) is faster and cheaper than cloud-only iteration. The homelab becomes your agent sandbox.
Tips
- Snapshot before major upgrades
- Keep secrets in a vault, not
.envfiles in git - Document every service in a single
SERVICES.mdat the repo root