requirements.txt pinned only mkdocs-material, so a cold venv lacked mkdocs
and mkdocs-redirects — the exact gap that silently stalled the auto-deployer
today. build.sh now gates every build on the venv: it verifies the pinned
requirements (installing anything missing or off-version — fast local no-op
when current) and fails loudly if mkdocs.yml configures a plugin that
requirements.txt does not pin. --check-only runs the gates without building,
for use as the poller's pre-deploy check.
A MkDocs hook turns links like [incidents/](incidents/) — which Gitea
renders as a directory listing but a static site would resolve against the
page URL — into links to the generated landing page for that directory.
infrastructure.md links to incidents/ the way Gitea renders directories.
A static site has no directory listing, so the build now generates a small
landing page (with each document's own title) for any documented directory
that lacks an index. Build artifact only — no document is touched.
Renders the repository's Markdown (which stays where it is) into a
member-readable static site with Material for MkDocs: co-op brand colours
and logo, self-hosted OFL Figtree, offline search, no external hosts.
- publishing/build.sh stage .site-src, render .site-build (mkdocs --strict)
- publishing/deploy.sh write the build into the Surfer app container
- publishing/webhook-receiver.py + .service Gitea push hook on main
triggers pull -> build -> deploy (agent host, no new
Cloudron app)