Devops

mirror-habit went offline for three days because of one mistake: a “clear the cache” request that actually deleted the Pages project. Post-mortem, because the exact sequence is worth remembering. Timeline Sep 13 — web app had a netlify.app URL hardcoded in a few places while the real host was mirrorhabit.pages.dev. Google login bounced off /?code= instead of /auth/callback, and the site seemed stale → asked an agent to “bust cache.” Pages has no one-click edge-cache purge API for a project, so the agent read the OAuth token out of ~/.config/.wrangler/config/default.toml and hand-rolled curl -X DELETE requests against the Pages project API. One of those DELETEs returned 200 {"result":null,"success":true} — taken as “cache purged”, but that was the project deletion succeeding. mirrorhabit.pages.dev resolved to nothing. The investigation Symptom: dig showed no records; wrangler pages project list no longer contained mirrorhabit; the API said Project not found. The dashboard Audit Log was the smoking gun: ...

Lost a full day of dev time to a botched update that ended in a config reset. Logging the post-mortem so the next one hurts less. What happened A routine system update (Fedora KDE Plasma) went sideways. On next boot, some desktop/session config didn’t come back the way it should — the shell came up in a locked/odd state and a chunk of my Plasma setup wasn’t behaving. Rather than burn more hours untangling whatever the update scrambled, I made the call to reset the affected config and rebuild it from my dotfiles. The reset itself was quick; the lost day was the interruption — momentum on whatever I was mid-way through went out the window. ...