post(case-studies): running production infrastructure solo — 162 containers, three hosts (EN+ZH) + og/banner
Deploy / build (push) Successful in 18s

The Phase C1 keystone asset (Story B). Publishes the infra case study:
- architecture: 3 hosts / 162 containers / 78 compose stacks with the per-host split
- incident record: the monitoring panels that lied, and the Passbolt cascade
- how the numbers are re-derived (verify_infra.py) rather than remembered
- no uptime percentage: availability is not measured, so the post says 'monitored'
- hire CTA (case-study convention)

EN + ZH twins, og + banner generated and measured (OG 5 tags/1 row, banner 8 lines delta 2).
This commit is contained in:
2026-10-06 08:04:02 +08:00
parent fbec241d0d
commit 67b844e3a0
6 changed files with 113 additions and 2 deletions
@@ -3,8 +3,10 @@ title: "Running Production Infrastructure Solo: 162 Containers Across Three Host
description: "One operator, three hosts, 162 containers in 78 compose stacks — Traefik, SSO, monitoring, mail, CI/CD and backups — and the two failures that changed how I verify my own numbers."
pubDate: 2026-10-06
category: case-studies
tags: [docker, traefik, monitoring, self-hosting, infrastructure, devops]
draft: true
tags: [docker, traefik, monitoring, infrastructure, devops]
ogImage: /og/running-production-infrastructure-solo.png
banner: /banners/running-production-infrastructure-solo.png
draft: false
---
## Why this matters