Files
computer-playbook/compose/package-cache
kevinveenbirkenbach 230d9a1e5e feat(cache): declare every cached upstream once and generate the rest
The package cache was configured in six places at once: the nginx upstream
map, the consumer compose override, pip.conf, .npmrc, the apt sources and the
twenty ensure_proxy_repo calls that bootstrap Nexus each spelled the same
hostnames, repository names and suites by hand. A new upstream meant editing
five files and hoping none was missed, and the docs told contributors to do
exactly that.

A role now declares what it needs under cache: in its meta/networks.yml, and
everything else is derived from it. svc-cache-package holds the general
upstreams; web-svc-libretranslate holds its own. All nine derived files are
generated and gitignored, so a second spelling of a hostname cannot exist.

utils.cache.hosts reads the declarations without PyYAML, because the .env
generator reaches them before any dependency is installed; it raises rather
than truncate when a comment sits at column 0 inside the block, which would
otherwise drop every declaration below it in silence. utils.cache.records
owns the Nexus record format and the Ubuntu mirror resolution, so the dev
stack and the role provision from one rendering.

A build may only resolve a cached host it can verify: the plain-HTTP hosts
are hijacked for every image, and the TLS hosts only for an image whose
Dockerfile installs the frontend CA. Hijacking all of them would fail every
pip and npm build with CERTIFICATE_VERIFY_FAILED.

svc-cache-package deploys the cache and its TLS frontend by calling the same
shell scripts the dev stack calls, rather than reimplementing them as tasks.
The role is invokable through the new svc-cache category and inert until a
host carries it.

Verified: the twenty Nexus payloads, the fifteen nginx server blocks and all
seven package-manager configs are byte-identical to the hand-written files
they replace, and the new category adds one role to the deploy order while
preserving the relative order of the other 180.

The role has not been deployed yet.
2026-09-27 16:28:48 +02:00
..

Package-Cache Wiring 📦

Client-side configuration bind-mounted into the infinito runner so that pip, npm, and apt route through the Sonatype Nexus 3 OSS pull-through proxy.

For services, activation, coverage, and operations of the local cache stack, see cache.md.

Files 📄

  • pip.conf: pip configuration. Mounted at /etc/pip.conf. Routes pip through pypi-proxy.
  • npmrc: npm configuration. Mounted at /root/.npmrc. Routes npm through npm-proxy.
  • apt/<distro>.list: apt sources, one file per INFINITO_DISTRO. The matching file is mounted at /etc/apt/sources.list.d/package-cache.list. apt/debian.list routes apt through apt-debian, apt/ubuntu.list through apt-ubuntu; the pacman/dnf distros get an empty file, because apt-get update fails as a whole on a single unreachable source and must not carry a foreign distro's entry.