0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-12 13:47:01 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 e17d004e17 fix(swarm-lab): answer lab AAAA queries locally

address=/<zone>/<ipv4> covers only A records, so every AAAA lookup for
the lab zone was forwarded to the public resolvers. When the manager
node lost its upstream mid-run, glibc callers (Playwright request
contexts) paid the full resolver timeout per lookup: 20s each, which
blew the 30s request budget and the 60s persona budget.

local=/<zone>/ makes dnsmasq authoritative for the zone, so AAAA is
answered as NODATA from config instead of leaving the lab. Same idiom
the tor onion template already uses.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-22 11:36:00 +02:00

coredns

refactor(env): move env/default.env to repo-root default.env and drop env/

2026-05-21 16:22:33 +02:00

package-cache

fix(package-cache): survive a flaky apt mirror

2026-08-04 19:33:04 +02:00

package-cache-frontend

style: delete every comment the comments-valid policy rejects

2026-08-18 03:22:02 +02:00

registry-cache

fix(registry-cache): bypass gcr.io / storage.googleapis.com / googleusercontent.com

2026-05-08 13:21:21 +02:00

swarm

fix(swarm-lab): answer lab AAAA queries locally

2026-08-22 11:36:00 +02:00

.gitignore

feat(compose): add pull-through registry-cache + reorg compose/ subdirs

2026-04-27 18:14:11 +02:00

cache.override.yml

fix(package-cache): survive a flaky apt mirror

2026-08-04 19:33:04 +02:00

cache.shared.override.yml

feat(worktree): isolated per-branch checkouts sharing one cache stack

2026-07-28 16:15:59 +02:00

noports.override.yml

fix(svc-runner): publish no dev-stack ports in nested DooD deploys

2026-07-10 18:43:34 +02:00

README.md

feat(compose): add pull-through registry-cache + reorg compose/ subdirs

2026-04-27 18:14:11 +02:00

worktree.override.yml

feat(worktree): isolated per-branch checkouts sharing one cache stack

2026-07-28 16:15:59 +02:00

README.md

Compose Configuration 🧩

This directory holds the static configuration assets consumed by the top-level compose.yml of the local development and CI testing stack.

Scope 📋

The directory MUST contain only files that are bind-mounted into a service defined in compose.yml.
The directory MUST NOT host application configuration that belongs to an Ansible role. Per-role compose payloads live under roles/<role>/templates/.
The directory MUST NOT host workflow scripts, test fixtures, or build helpers. Those belong under scripts/ or tests/.

Layout 🗂️

Each compose service that needs static configuration owns a sub-directory whose name matches the service. New service-specific config MUST go into the matching sub-directory rather than at the compose/ root.

For the rules that govern compose.yml itself (env-variable contract, profile gating, resource caps), see compose.yml.md.