Deployment

BlastoDB is built by GitHub Actions and hosted on GitHub Pages at www.blastodb.com.

Hosting

BlastoDB is hosted on GitHub using GitHub Pages. The public domain is www.blastodb.com.

Branches

The Git repository has the following branches, with the following purposes:

Branch	Role
`dev`	Developer work (code/features). Build-checked, not deployed.
`staging`	Content from the CMS lands here and is build-checked before release.
`main`	The live site. Every push deploys.

Workflow	Trigger	Does
`check.yml` (Build Check)	push to `staging`/`dev`, PR to `main`	Builds the site; fails on broken content. No deploy.
`publish.yml` (Publish)	daily 05:30 UTC + manual	Build-gates `staging`, merges `staging → main`, dispatches Deploy and Sync.
`deploy.yml` (Build and Deploy Live Site)	push to `main` + manual	Builds with `PATH_PREFIX=/blastodb`, deploys to GitHub Pages.
`sync-staging.yml` (Sync)	push to `main` + manual	Merges `main → staging` to keep them aligned.

The editorial workflow from a system perspective is:

An editor saves in the CMS → a commit on staging.
Build Check runs on staging; a broken build blocks the release.
Once a day at 05:30 UTC, the Publish workflow on GitHub actions build-gates staging and merges it into main (it can also be run on demand).
The push to main triggers Deploy, which builds and publishes to GitHub Pages.

So routine edits go live in the next daily publish, not instantly. To publish sooner, run the Publish workflow by hand — see Checking & Publishing.