Deployment Guides
The infrastructure patterns I build and run on my own hardware, documented as guides with real configuration excerpts — not as downloadable products. Every guide follows the same shape: the architecture in two sentences, a deployment example taken from the actual compose file, the environment variables that matter, and a production checklist. The FAQ sections answer the questions that usually only surface after the first outage.
What the guides cover
The foundation pair: TLS reverse proxy with Let's Encrypt and CrowdSec is the front door for everything else — automated certificates, intrusion prevention at the edge. PostgreSQL and Redis, tuned instead of defaulted is the state layer almost every application needs, backups included.
Seeing and storing: The observability stack — Prometheus, Loki, Grafana — watches everything else, including the alerts worth writing before the dashboards. MinIO with an rclone backup agent gives you S3-compatible, versioned backups without a cloud bill.
Platforms and applications: k3s with MetalLB and Longhorn is the lab-to-production Kubernetes path. Self-hosted AI with Ollama, Open WebUI and LiteLLM runs LLMs on your own GPU behind one OpenAI-compatible endpoint. n8n in queue mode is the automation layer that survives restarts and workload spikes.
A sensible reading order
Start with the reverse proxy — nearly every other guide assumes TLS in front. Add observability second, because everything after that is easier to debug with metrics and logs in place. From there, pick by need: databases if you build applications, MinIO if you owe yourself honest backups, k3s if Kubernetes is the goal, n8n and the AI stack when workload or curiosity demands it. Each guide stands alone; the shared assumption is Docker Compose and a Linux host you control.
Deutsche Version
Die Infrastruktur-Muster, die ich auf eigener Hardware baue und betreibe — dokumentiert als Guides mit echten Konfigurationsauszügen, nicht als herunterladbare Produkte. Jeder Guide folgt demselben Aufbau: die Architektur in zwei Sätzen, ein Deployment-Beispiel aus der realen Compose-Datei, die wichtigen Umgebungsvariablen und eine Produktions-Checkliste. Die FAQ-Sektionen beantworten die Fragen, die sonst meist erst nach dem ersten Ausfall auftauchen.
Das Fundament: Der TLS-Reverse-Proxy mit Let's Encrypt und CrowdSec ist die Eingangstür für alles andere, der getunte PostgreSQL-/Redis-Stack die Datenschicht mit Backups. : der und . : , und .