0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-08 11:46:35 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.8 99ed66d716 fix(svc-runner): publish no dev-stack ports in nested DooD deploys

- compose/noports.override.yml drops every published port via !override
- compose_file_args appends it when INFINITO_PUBLISH_PORTS=false
- runner instances set the flag; default true keeps other flows unchanged
- central yaml loader + ansible-lint config accept compose merge tags

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-10 18:43:34 +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(svc-runner): fix piop same root issue as apt

2026-06-24 18:31:14 +02:00

package-cache-frontend

Merge remote-tracking branch 'upstream/main' into feature/self-host-runners

2026-06-27 23:45:38 +02:00

registry-cache

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

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

.gitignore

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

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

cache.override.yml

Merge branch 'main' into feature/swarm-nfs

2026-07-01 05:37:36 +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

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.