mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-09 20:26:33 +00:00
kevinveenbirkenbachandClaude Opus 5
575a5a87ac
Every script a role ships now lives under `files/<language>/`, and the unit
suite is split the same way: `tests/unit/python/` beside new sibling trees for
the other languages. `tests/lint/filesystem/test_role_files_layout.py` keeps it
that way; directories whose shape is dictated from outside carry a `.nocheck`
naming the constraint (Docker build contexts, WordPress mu-plugins, the Joomla
extension, Odoo addons, Playwright suites, the `files/test/test.sh` harness
that `test-e2e-cli` resolves generically).
This cannot be applied in halves. Moving a file and repointing what names it
are the same change: 14 references resolve only at deploy time, so the tree is
green either before or after, never between.
Those 14 were found by static resolution over every reference class, not by the
test suite -- a full `make quality-high` was green while all of them were
broken:
* 7 `src:` values built from a role variable holding a bare filename
(svc-bkp-remote-2-local, decidim, espocrm, friendica, joomla, pixelfed x2).
The variable doubles as the destination name inside the container, so the
language segment belongs at the call site, not in the variable.
* `sys-service/tasks/04_base.yml` resolved every consumer's systemd script
through `first_found(..., errors='strict')` over `files/script.{sh,py}`.
18 roles ship exactly that and have no template fallback: the play would
have died on each.
* `sys-front-inj-javascript` fell back to `<role>/files/javascript.js`; the
interface now reads `files/javascript/javascript.js`.
* `sys-front-inj-logout/templates/head_sub.j2` built the cache-busting mtime
path through `path_absolute(... 'files', ...)`.
* 4 `ansible.builtin.script:` invocations naming a bare command
(pull.py, prune.sh, set_postgres_superuser_password.sh, ganesha-serve.sh).
* `dev-python/files/shell/install.sh` pointed at a sibling role's script.
Depth-dependent paths inside the moved trees were bumped accordingly: 59
`parents[N]` computations, 12 relative climbs, and the per-role recover CLI,
whose path `cli/administration/recover/recoverers.py` still assembled from the
pre-move location.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CA Trust Scripts 🔐
This directory contains platform-specific scripts for trusting the Infinito Root CA certificate on the developer's machine. For the canonical Make target index that invokes these helpers, see make.md.
All scripts extract the Root CA from a running Infinito container and install it into the appropriate system trust store, so that browsers and tools accept *.infinito.example TLS certificates without warnings.
Scripts 📄
linux.sh 🐧
Trusts the Infinito Root CA on the Linux host system.
- Extracts
root-ca.crtfrom the running Infinito container viadocker cp - Places it under
/etc/infinito.nexus/ca/root-ca.crt - Installs it into the system trust store via
roles/sys-ca-selfsigned/files/shell/with-ca-trust.sh
Requires INFINITO_CONTAINER to be set to the name of the running container.
wsl2.sh 🪟
Trusts the Infinito Root CA on Windows from inside a WSL2 environment. Only executes when running on WSL2 (detected via /proc/version).
- Extracts
root-ca.crtfrom the running container and copies it to the WindowsDownloadsfolder - Imports the certificate into the Windows CurrentUser Root trust store via PowerShell (no admin required)
- Discovers all configured domains from the nginx config inside the container
- Updates the Windows hosts file (
C:\Windows\System32\drivers\etc\hosts) with127.0.0.1entries for all discovered domains (requires one UAC confirmation)
Related 🔗
../. TLS administration scriptsroles/sys-ca-selfsigned/. generates the self-signed Root CA inside the container