mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 5
3d93c81f70
The split left the swarm track without any teardown: a `base swarm` run started the development stack in base/04_bootstrap.sh and never brought it down, so it leaked AppArmor, dev DNS and IPv6 state onto the host and ran the swarm cluster alongside a live dev stack the old suite had already released. The old single job ran `make compose-down` + `make environment-teardown` as step 10, immediately before 12_swarm.sh and 13_roundtrip.sh. The swarm track now reproduces exactly that: 01_teardown releases the stack before 02_zombie and 03_roundtrip (which are byte-identical to the old steps apart from their source path), and 04_teardown leaves the host clean — something the old suite never did, since it ended on the roundtrip's restarted stack. Both closing steps and the new leading one share utils/teardown.sh so the teardown cannot drift between tracks. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Script Collection
This directory contains automation scripts used across the project.
-
system/ contains host and system-facing helpers.
-
container/ contains helpers that run inside the local container.
-
github/ contains GitHub workflow helper scripts.
-
For the canonical Make target index, see make.md.
-
🛠️ Organize operational helpers for development, CI, release, and maintenance
-
🧭 Separate responsibilities into focused subdirectories with clear scope
-
📚 Keep script-based workflows discoverable and easier to navigate
The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.