CherryBomb

Deploying

_site/ is plain static files, so anything that serves files serves a Cherry site. The paved road is GitHub Pages, and it is one verb long.

The generated workflow

$ cherry gen.action

Wrote .github/workflows/pages.yml (CNAME: cherrybomb.dev) — enable it once under Settings → Pages → Source → GitHub Actions.

On every push to main (choose another with --branch), the workflow:

  1. installs Cherry,
  2. runs cherry check --strict, so a broken link or a missing description fails the push instead of reaching production,
  3. runs cherry build,
  4. uploads _site/ and deploys it with GitHub's Pages actions.

It also writes .nojekyll (so nothing gets reprocessed) and, when your url is a custom domain, a CNAME file. One-time repo setup: Settings, then Pages, then Source: GitHub Actions.

Pagefind needs Node in CI

search: "cherry" needs nothing anywhere, which is why this site uses it. If you chose search: "pagefind", the build shells out to npx pagefind at the end. GitHub's Ubuntu runners ship with Node, so the generated workflow works as-is; add a setup-node step if you want the version pinned and the npm cache warm.

Custom domains

Set url to the real domain and everything follows: canonical links, feeds, sitemap, the workflow's CNAME. Point DNS at GitHub Pages (an A/ALIAS set for an apex, a CNAME record for a subdomain), then turn on Enforce HTTPS in the repo's Pages settings once the certificate is issued. This site is deployed exactly this way; its config is in the open.

Project pages and base_path

Serving under username.github.io/repo means every URL needs a /repo prefix. That is one config key:

base_path: "/repo"

Links, images, feed URLs, search assets, and component src/poster paths are all rewritten. The verifier resolves links against the same rule, so a hardcoded absolute path that would break under the prefix is caught before it ships.

Anywhere else

cherry build && rsync -a _site/ server:/var/www/site/ is a complete deploy. Builds are deterministic, so rsync transfers only what actually changed, and two machines building the same commit produce identical trees. Netlify, Cloudflare Pages, and friends work the same way: point them at cherry build and _site/.