mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-11 13:17:07 +00:00
kevinveenbirkenbachandClaude Opus 4.7
a94dfe87e2
New role that runs registry:2 in pull-through proxy mode on the swarm manager. Worker nodes' daemon.json gets a registry-mirrors entry plus the corresponding insecure-registries entry so plain-HTTP traffic to the cache is permitted. The role's inventory group lists exactly one host (manager) so the new inventory-driven topology model resolves DEPLOYMENT_MODE to compose for the cache itself. Within a single deploy run, the three swarm workers all pull the same base images via the cache instead of hitting registry-1.docker.io three separate times. Measured speedup on iter26 vs the no-cache iter21 baseline: pkgmgr/apt-install steps 2.4-2.8x faster, Docker image pulls 1.8-2.8x faster. Cross-iter cache persistence is intentionally out of scope: act recycles the DinD nodes between runs so the cache volume is wiped each time. Cross-run reuse would require either bind-mounting the cache from the host or pointing daemon.json at the dev compose stack's registry-cache; both are tracked separately. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Test Utilities 🧪
This directory holds the operational side of testing in Infinito.Nexus.
These assets are meant to support confidence, not ceremony. They help the project validate real-world behavior across local development, CI environments, and deployment-oriented smoke tests. The emphasis is on practical feedback: when something breaks, the surrounding test tooling should make the failure easier to understand, easier to reproduce, and easier to clean up. 🚀
Good changes in this area usually make the test experience more:
- repeatable
- diagnosable
- environment-aware
- safe to rerun
The ideal outcome is boring reliability: contributors should be able to trust that a test run says something meaningful about the system, not just about the machine that happened to execute it. ✅