0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 03:38:23 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 5 28474f38c0 fix(swarm): preinstall python3-apt in the test node image

Without the bindings the ansible apt module installs them itself mid-play, and the dist-upgrade that follows deadlocks: the module spins in user code while apt-get blocks writing to a full stderr pipe. It ran that way on all five nodes for three hours.

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

2026-08-07 17:05:51 +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

fix(package-cache): restore apt slash redirect

2026-08-04 20:16:36 +02:00

registry-cache

…

swarm

fix(swarm): preinstall python3-apt in the test node image

2026-08-07 17:05:51 +02:00

.gitignore

…

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

…

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.