0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-09 20:26:33 +00:00

Files

T

evangelostsak fd89f3c54c fix(swarm-test): never disable wireguard in the swarm drill

The drill strips the services it cannot run without from the incoming disable
list, and wireguard was not among them. For an app whose own graph does not
reach it, the provision step disabled the service while extend_inventory had
already placed svc-net-wireguard on every swarm host, and the services
disabler rejected the pair:

  service 'wireguard' is disabled, but provider role 'svc-net-wireguard' is
  still active in .../devices.yml

svc-swarm-node declares the service required for exactly this reason, so the
drill has no more business disabling it than it has disabling node.

2026-09-25 00:16:24 +02:00

container

…

docker

fix(cache): retry the cert generator's image pull

2026-09-15 04:05:07 +02:00

git

…

github

feat(ci): deploy only the variants a change reaches

2026-09-21 22:51:03 +02:00

image

perf(ci): fold the matrix job into the image job and stream its output

2026-09-16 21:48:12 +02:00

install

fix(install): keep the collection check inside the slice that runs it

2026-09-18 03:03:37 +02:00

inventory

…

lint

fix(test-e2e-playwright): give every Playwright timeout one source

2026-09-12 12:04:27 +02:00

make

fix(make): stop a repeated lint target from hiding its own failure

2026-09-19 07:41:01 +02:00

README.md

Script Collection

This directory contains automation scripts used across the project.

system/ contains host and system-facing helpers.
container/ contains helpers that run inside the local container.
github/ contains GitHub workflow helper scripts.
For the canonical Make target index, see make.md.
🛠️ Organize operational helpers for development, CI, release, and maintenance
🧭 Separate responsibilities into focused subdirectories with clear scope
📚 Keep script-based workflows discoverable and easier to navigate

The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.