mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
The 16.2.0 release commit (e2501cb1de) shipped a locally generated `compose/package-cache-frontend/upstreams.conf`, the output of the cache generator that only exists on the feature branches (230d9a1e5e). It adds TLS server blocks for argos-net.com, huggingface.co, index.crates.io, registry.ollama.ai and static.crates.io, but main's `cert-gen.sh` issues no certificates for them. nginx then dies on start with cannot load certificate "/etc/nginx/certs/argos-net.com.crt" the frontend stays unhealthy, pypi.org on the runner refuses connections, and `make install-lint` fails in every workspace job (run 39482585010). Restore the file byte for byte to its state before the release (blobb5c5ef08e7), the version every workspace job passed with in run 39443109355. Co-Authored-By: Claude Opus 5.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.