System 1 min read active
Client hosting platform
Two VPS hosts, Caddy, BunnyCDN, Payload, Umami, Komodo, and a preference for boring release swaps.
T
hostingsystemsvpscdnobservabilitynixoscaddykomodobunnycdnpayloadumami
The platform is split into a public web host and an internal services host. The public host serves static files through Caddy, while Payload, Umami, and deployment orchestration live away from public reader traffic.
Current shape
- client-web-01 serves static releases and reverse-proxy front doors
- internal-01 runs Payload, Umami, Komodo, and supporting services
- BunnyCDN handles DNS and global CDN delivery
- Releases use build artifacts, rsync, symlink swaps, and cache purge
Sanitized notes
Public system pages should describe the shape and decisions, not secrets, private hostnames, or operational details that make future-me wince.
Things I still want to improve
- Tighter rebuild queue visibility
- A nicer approval packet for content-only changes
- More automatic checks around cache headers and stale release cleanup