I test what ships and publish what I find, failures included: 100+ public repositories, every restore script run by CI, every finding on the ledger with its rule.
One of fewer than 250 Docker Captains worldwide, a CNCF Ambassador, and Technical Editor of "Docker and Kubernetes Security."
Production-tested. Partner links.
🛸 Proton VPN – Encrypted tunnel
🔐 Proton Pass – Zero-knowledge vault
🦑 GitKraken Pro – Visual Git client
🐧 Linux Foundation – Code: VALDEMAR
📚 ExpertEdge – Code: VALDEMAR
4 posts tagged
A backup verified by restore is the only kind that exists. Twelve days of OK over a volume nothing wrote to, and 47 templates' restore scripts CI never ran.
Restore drills that measure RTO on a machine that never ran the stack, 47 templates weekly. Every same-host restore passed. The first clean one answered 500.
A Docker health check whose pattern matches the shell running it can never go red. How to find the checks in your fleet that never failed, and prove each one.
The terminal is the window, the shell runs your commands, the prompt says it is ready, the command line is the idea. Plain definitions, examples, a cheat sheet.
