docs: mention the check workflow in the README

This commit is contained in:
squid 2026-11-15 10:27:27 +01:00
commit 1ebc730247

View file

@ -67,3 +67,5 @@ The texts are released under CC BY-SA 4.0, see `LICENSE`. The code and the logo
Pushing to `main` publishes the site. A post-receive hook in the Forgejo repository touches a trigger file, `deploy-kmalloc-site.path` on the server notices it and runs `deploy-kmalloc-site`. The script builds `main` into a temporary directory with the pinned motorino and mirrors it into the web root. It downloads the binary once, checks it against the hash in `.motorino-version` and keeps it in `/var/cache/kmalloc-deploy`. If the hash or the build is wrong nothing is copied. Pushing to `main` publishes the site. A post-receive hook in the Forgejo repository touches a trigger file, `deploy-kmalloc-site.path` on the server notices it and runs `deploy-kmalloc-site`. The script builds `main` into a temporary directory with the pinned motorino and mirrors it into the web root. It downloads the binary once, checks it against the hash in `.motorino-version` and keeps it in `/var/cache/kmalloc-deploy`. If the hash or the build is wrong nothing is copied.
To move to a new motorino: take the version and the SHA-256 from its release and write them in `.motorino-version`. To move to a new motorino: take the version and the SHA-256 from its release and write them in `.motorino-version`.
A Forgejo Actions workflow (`.forgejo/workflows/check.yml`) builds the site with the pinned motorino and runs the Nu HTML Checker on every page, on every push to `main` and on every pull request, on the shared runner of git.kmalloc.org. The publishing itself stays the hook on the server.