Strange Duck Docs
Welcome to the internal technical and operational documentation for Strange Duck.
This site is the canonical reference for how Strange Duck systems are built, operated, maintained, backed up, recovered, and supported.
Start here
Infrastructure
Servers, hosting, DNS, email, calendars, backups, monitoring, and core technical architecture.
Operations
Operational processes, monitoring rules, alerting, Website Rescue, and day-to-day system management.
Products
Technical documentation for Strange Duck products and services.
Runbooks
Step-by-step procedures for deployment, recovery, maintenance, incidents, and other repeatable operational tasks.
Current priorities
- Document the Strange Duck infrastructure
- Build the master systems register
- Document DNS and email architecture
- Document Strange Duck Ops and monitoring
- Document deployment and recovery procedures
- Complete backup-system migration documentation
- Record product architecture as systems are built
Documentation rule
If it would be painful to rediscover later, document it now.
Infrastructure changes involving backups, cron, DNS, monitoring, email routing, server accounts, SSH keys, deployment, recovery, or production architecture should be documented as they are made.
Important
This documentation may contain operational detail that should not be made public.
Do not store passwords, API keys, recovery codes, private keys, or other secrets directly in these pages.