docs(ops): fix rollback runbook — no sqlite3 CLI on the deploy host - #46
Open
DanielGGordon wants to merge 1 commit into
Open
DanielGGordon wants to merge 1 commit into
DanielGGordon wants to merge 1 commit into
Conversation
Every command in the runbook shelled out to `sqlite3`, which is not installed here. Replaced with Node 24's built-in node:sqlite, and switched the database backup from `.backup` to `VACUUM INTO`, which is safe against a live WAL database and yields a consistent single-file snapshot. Verified end to end by taking the actual pre-deploy backup: ~/backups/t3-pre-sidebarv2-2026-07-27/ — 334 MB snapshot reading back at ledger 33/ProjectionThreadRestartRequest with 202 threads, plus settings.json, keybindings.json and secrets/ (none of which are in git).
github-actions
Bot
added
vouch:trusted
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #45.
Every command in
docs/operations/rollback-2026-07-27-sync.mdshelled out tosqlite3, which is not installed on the deploy host. A runbook you only discover is broken during an incident is worse than no runbook.Replaced with Node 24's built-in
node:sqlite, and switched the database backup from.backuptoVACUUM INTO— safe against a live WAL database and yields a consistent single-file snapshot.Verified by actually taking the pre-deploy backup rather than just editing the doc:
🤖 Generated with Claude Code