0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-06 19:01:54 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.7 ff54c3fda9 fix(cache): mark apt-debian-security upstream as nocheck for URL test

`test_public_http_urls_are_reachable` flagged
`http://deb.debian.org/debian-security` as a hard fail (HTTP 404),
breaking the test-external CI gate.

The URL is correct — apt clients fetch concrete files underneath
`dists/bookworm-security/`, all of which resolve to 200. Only a bare
GET on the redirector path returns 404 because the redirector does
not serve a directory index. The same convention (`# nocheck: url`)
already covers raw-packagist on line 121 for the same reason.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-04 09:12:34 +02:00

cache

fix(cache): mark apt-debian-security upstream as nocheck for URL test

2026-05-04 09:12:34 +02:00

entry.sh

Refactor lint tooling and shell scripts

2026-03-18 12:37:31 +01:00

healthcheck.sh

Refactor lint tooling and shell scripts

2026-03-18 12:37:31 +01:00

README.md

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

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

README.md

Docker Runner Scripts 🐳

Shell helpers that run inside the infinito runner container defined by the top-level compose.yml. They cover container lifecycle (entry, healthcheck) and integration with peer compose services (e.g. the registry-cache pull-through proxy).

Scope 📋

This directory MUST contain only scripts that execute inside the infinito container, either as the container entrypoint, as a Docker HEALTHCHECK, or as a systemd unit hook.
This directory MUST NOT host host-side tooling. Scripts that run on the developer or CI host belong under their workflow-specific path (for example scripts/tests/, scripts/image/, scripts/meta/).
This directory MUST NOT host application logic that belongs to an Ansible role.

Bind-mounted scripts 🔗

A script that is bind-mounted from this directory into a fixed in-container path (see compose.yml) MUST keep its git executable bit, because Docker bind-mounts preserve host file permissions and the in-container caller (systemd, dockerd, the entrypoint) cannot recover from a non-executable mount.

When a new script is added with a bind-mount target, its purpose and in-container target path SHOULD be documented at the call site (the matching compose/<service>/ README, or compose.yml.md).

Distro portability 🌐

A script in this directory MUST work across every distro variant that the runner image is built for (currently Debian, Ubuntu, Arch, Fedora, CentOS). Tool availability differs across these variants, so a script SHOULD branch on command -v <tool> rather than on distro IDs.