mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-07 03:15:56 +00:00
kevinveenbirkenbachandClaude Opus 5
7254227b1b
The restore cycle stops every subject of the host, replays into the database services alone, and starts the rest again at the very end. Any exit in between skips that last step, so the host keeps its subjects down - and nothing recorded it. The next deploy then failed on a symptom of the teardown rather than on whatever ended the drill. It cost two runs: once 'rake db:migrate' against a database the cycle had emptied but not yet replayed, once Redis::CannotConnectError because the cycle never restarted redis. Both times the message pointed away from the cause, and fixing what it named would have fixed nothing. A trap armed before the teardown now records the teardown and the exit code, and mode=update refuses to run while that record stands. purge=true and mode=reinstall pass, because both rebuild the state the drill destroyed; a completed cycle clears the record itself. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Local Deploy Test Scripts 🧪
This file describes the local helpers outside deploy/.
For executable local deploy flows, use deploy/README.md.
For inventory reset helpers, use reset/README.md.
For cleanup helpers, use purge/README.md.
For container exec helpers, use exec/README.md.
For the canonical Make target index that invokes these helpers, see make.md.
Prerequisites
- Run commands from the repository root.
- Docker and Docker Compose are available locally.
- If you run scripts directly, load the defaults with
source scripts/meta/env/all.sh.