feat: homelab case study from live infra; Traefik-based deploy

- rewrote homelab (content + topology diagram + stack) from a live inspection of the host:
  Ubuntu 24.04, ~30 Docker services behind Traefik (Cloudflare-fronted, TLS, HTTP/3),
  Authentik SSO forward-auth, CrowdSec, Pi-hole, self-hosted Gitea + CI runner, socket-proxy,
  per-app network isolation; WordPress framed as being decommissioned (not future arch)
- deploy: docker-compose now uses Traefik labels + traefik_proxy network (was assumed nginx
  edge); .env.example adds SITE_HOST/TRAEFIK_ENTRYPOINT; colophon + ARCHITECTURE/DOCKER/
  DEPLOYMENT specs corrected nginx-edge -> Traefik (site container still serves via nginx)
- PROJECT_STATUS: pre-launch checklist updated; infra section added

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
cesnimda
2026-07-04 11:23:09 +02:00
parent a10418ab93
commit bfa8cfd357
8 changed files with 129 additions and 84 deletions
+4 -2
View File
@@ -14,5 +14,7 @@ RELAY_WINDOW_SECONDS=600
# --- Site build ---
PUBLIC_SITE_URL=https://cesnimda.co.uk
# --- Infra ---
PROXY_NETWORK=web # name of the existing external reverse-proxy docker network
# --- Infra (Traefik host reverse proxy) ---
PROXY_NETWORK=traefik_proxy # existing external Traefik docker network
SITE_HOST=cesnimda.co.uk # Host rule for the Traefik routers
TRAEFIK_ENTRYPOINT=websecure-external # Traefik entrypoint name on the host