GeoHarness

Adapters and runtime detection

GeoHarness builds almost any static site. An adapter knows how to detect a kind of project, build it and list its pages; GeoHarness runs every adapter's detection, picks the most confident one and logs the evidence it found.

Updated

How does GeoHarness choose an adapter?

Which adapters are there?

AdapterDetected whenWhat it does
worker-assetsA wrangler config with assets.directoryBuilds, writes into the assets directory and deploys with your own wrangler config, so your Worker code and bindings stay in charge
sveltekit-staticA Svelte config using @sveltejs/adapter-staticRuns the build; output is adapter-static's directory
vite-prerenderA Vite config and an empty SPA mount point in index.htmlBuilds, then renders / and every llms route (or prerender.routes) with headless Chromium so pages carry real text
commandThe build-command input is setRuns it (no shell) and reads output-dir; works for any language
pythontools/build.py, or pyproject.toml with a build-commandRuns the build; attaches markdown sources it finds to their pages
npmpackage.json with a build scriptRuns the script; output from output-dir or the generator's config
makeA Makefile with a build targetRuns make build; reads output-dir
staticoutput-dir/index.html exists and no build-commandNothing to build: the committed output is used as is

How are build commands run?

Commands run as an argument vector, never through a shell. Quotes group words; pipes, redirects, ;, &, $ and globs are rejected, so an input can never inject a command. Put multi-step builds in a script and call it.

Pages are every .html file in the output except 404.html. A page's lastmod is the date of the last commit that touched it (or its markdown source), never the time of the build.