mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 04:06:42 +00:00
kevinveenbirkenbachandClaude Opus 5
a0a24e2c0e
server() now resolves a translation endpoint in three steps: use the running service, rebuild when the host has a GPU but no accelerated deploy left its stamp, otherwise deploy. A plain run therefore costs nothing, and the rebuild fires once, on the move from a CPU-built container to an accelerated one. deploy() brings the runner up, waits for State.Running and deploys the role inside it. The exec steps address `docker compose exec i18n` directly: cli.administration.deploy.development exec hardcodes the `infinito` service (compose.py:261), so every deploy through it silently ran in the main container, where mailu already holds port 25 and postfix cannot start. check=True stops a failing step instead of carrying on against the wrong target. The deploy router writes its pid to build/deploy.pid, which survives the exec into the subscripts, and deploying() refuses a translation while that process lives. The running deploy is left untouched. 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.