mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-12 13:47:01 +00:00
kevinveenbirkenbachandClaude Opus 5
05f425ea51
The quiesce guard spelled the dev container as the literal infinito_nexus_debian, so it only ever matched a checkout whose .env was generated for debian without a project prefix. It missed the self-hosted runner form infinito_<project>_nexus_<distro>, any custom.env pin, and any .env generated for another distro — and it missed them silently, because a non-matching grep just skips the block and leaves the competing onion publisher running. INFINITO_CONTAINER is the SPOT for that name: compose.yml uses it as container_name, and scripts/meta/env/load.sh (already sourced at line 19) exports it. Proven against the container running on the author's host: the literal does not match it, the variable does. The outer `docker ps | grep -qx` pre-check is gone with it — `docker exec` on an absent container already exits non-zero with stderr suppressed, and the `if` absorbs that even under `set -euo pipefail`. The variable joins the line-21 assertion so a broken env fails by name instead of dying inside a pipeline subshell, which would reproduce exactly the silent-skip class this commit removes. compose.yml already requires the same variable with `:?`, so this is not a new demand on the environment. tests/lint/repository/test_no_hardcoded_container_name.py pins it: run against the pre-fix file it flags all three lines, and it stays green on the distro-agnostic spellings in stack_refresh.sh and worktree/up.sh. 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.