Operations¶
Purpose¶
Day-2 runbooks: checking whether things are healthy, reading logs, inspecting D1/R2, rolling back, and responding to an incident. Every command in this section is labeled with its safety class.
Safety labels used throughout¶
| Label | Meaning |
|---|---|
[READ-ONLY] |
Reads state, changes nothing |
[SAFE LOCAL] |
Mutates only local emulation (.wrangler/, local D1) |
[MUTATING] |
Changes real state - could be local or remote depending on context, check the command |
[REMOTE / MUTATING] |
Changes real Cloudflare account state (D1, R2, Worker secrets) |
[PRODUCTION] |
Directly affects live traffic on a real domain |
Pages in this section¶
- Verification - is the platform actually healthy right now?
- Monitoring - what observability exists (and what doesn't).
- Logs -
wrangler tailper Worker. - D1 Operations - safe reads, and what a mutation actually requires.
- R2 Operations - inspecting bucket contents safely.
- Rollback - the manual procedure (no automated rollback exists).
- Incident Response - what to do when something's actually broken.
- Troubleshooting - cross-cutting symptom → cause table.