mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 12:17:13 +00:00
rpardini/docker-registry-proxy SSL-bumps and caches only the registries its REGISTRIES env names; Docker Hub is hardcoded in its entrypoint. A registry the list omits is still tunnelled, so its pulls succeed at full upstream cost and leave no line in the proxy log. The list was the image default and omitted mcr.microsoft.com, registry.gitlab.com and registry.opencode.de, all three of which roles declare images on. Deriving it from every image: in roles/**/meta/services.yml keeps it complete by construction. BASE carries the two registries that were configured before and that no role image names, so the switch to a derived list cannot drop them. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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/ortests/.
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.