mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
kevinveenbirkenbachandClaude Opus 4.7
1dd8d3f5c0
Introduces a `registry-cache` service (rpardini/docker-registry-proxy) in the `ci` profile that MITM-caches every outbound docker registry pull made by `infinito`'s inner dockerd, drastically cutting bandwidth on re-deploys, parallel CI shards, and local fresh-purges. Wiring (all bind-mounted via compose.yml, no Dockerfile or entry.sh staging, so edits hot-reload on next container start): - CA bundle at /opt/registry-cache-ca (read-only), - systemd drop-in at /etc/systemd/system/docker.service.d/registry-cache-proxy.conf, - registry-cache-ca.sh at /usr/local/bin/registry-cache-ca.sh. The drop-in registers registry-cache-ca.sh as ExecStartPre. Compose gates `infinito` on `registry-cache` `service_healthy` so the CA is on disk before dockerd boots; the install script supports both Debian (`update-ca-certificates`) and Arch/Fedora (`update-ca-trust extract`) trust stores, detected by command availability. Also reorganizes compose/ into per-service subdirectories (compose/coredns/, compose/registry-cache/) with README.md per directory following the documentation guidelines, adds scripts/docker/README.md, and nests the registry-cache host paths under /tmp/infinito/core/ (mirror/ for blobs, ca/ for the MITM CA bundle). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
27 lines
998 B
Markdown
27 lines
998 B
Markdown
# Compose Configuration 🧩
|
|
|
|
This directory holds the static configuration assets consumed by the
|
|
top-level [compose.yml](../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](../docs/contributing/artefact/files/compose.yml.md).
|