Part of #27: Ken will host the page on his server.
New workflow .gitea/workflows/pages.yml:
on every push to main (data PRs included), it builds the site (npm run build → dist/);
it force-pushes the result as the only commit of the pages branch.
Ken's web server serves that branch as plain files, kept in step with a git-sync sidecar or a git pull on a timer. The repository is public, so his server needs no token. Only the build output is on pages.
forge.yaml: a note to set site: to the address once it's live, so the page's links and the dataset metadata use it.
Part of #27: Ken will host the page on his server.
- **New workflow `.gitea/workflows/pages.yml`:**
- on every push to `main` (data PRs included), it builds the site (`npm run build` → `dist/`);
- it force-pushes the result as the only commit of the `pages` branch.
Ken's web server serves that branch as plain files, kept in step with a git-sync sidecar or a `git pull` on a timer. The repository is public, so his server needs no token. Only the build output is on `pages`.
- **`forge.yaml`:** a note to set `site:` to the address once it's live, so the page's links and the dataset metadata use it.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Every push to main builds the static site (npm run build -> dist/) and force-pushes it as the only commit of
the `pages` branch. Ken's web server serves that branch (a git-sync sidecar or a pull on a timer): nothing
on his server needs a secret, since the repository is public, and the site updates within minutes of every
merge, data PRs included.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01UCzTd31GphpMXDhQqWrCMQ
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #27: Ken will host the page on his server.
New workflow
.gitea/workflows/pages.yml:main(data PRs included), it builds the site (npm run build→dist/);pagesbranch.Ken's web server serves that branch as plain files, kept in step with a git-sync sidecar or a
git pullon a timer. The repository is public, so his server needs no token. Only the build output is onpages.forge.yaml: a note to setsite:to the address once it's live, so the page's links and the dataset metadata use it.🤖 Generated with Claude Code
pagesbranch for Ken's server to serve (#27)