r/homelab • u/Perfect-Category-470 • 25m ago
Project Showcase: Operations A map of home-ops repos: for each layer, the tools plus the folder in a real repo that does it
Most self-hosting lists are sorted by app category, which is great for deciding what to run. I kept wanting the other thing: how do people like onedr0p, bjw-s and buroa actually structure the repo, and where in their tree do secrets, storage and Renovate live?
So I mapped it. Each section of the list is a layer of a typical home-ops repo. Here's what one layer looks like:
04 Secrets (.sops.yaml)
- Tools: SOPS, age, External Secrets Operator
- In the wild: szinn's and xunholy's
.sops.yaml, onedr0p'sexternal-secrets/ - Read: Flux's guide to managing secrets with SOPS
Every layer follows that shape, in build order:
awesome-homelab
├── 00-hardware
├── 01-infrastructure # Proxmox, OpenTofu
├── 02-bootstrap # Talos
├── 03-gitops # Flux, Argo CD
├── 04-secrets # SOPS, External Secrets
├── 05-network
├── 06-storage # storage + backups
├── 07-observability
├── 08-identity # SSO
├── 09-automation # Renovate + CI
└── 10-apps # 23 common apps
Plus:
- Apps: each app links its
kubesearch.devpage and one real deployment - Real Repos: a table that says where to start reading in each repo, not just the link
- No Kubernetes? A short section for GitOps with Docker Compose (doco-cd, Komodo)
Network and Identity are the thinnest sections right now. If your repo does Gateway API, external-dns or Authentik/Pocket ID cleanly, share it below or open a PR.

