Cloudflare Deployment
pnpm run setup provisions and deploys everything. See Set up and deploy.
What gets created
Section titled “What gets created”| Resource | Purpose |
|---|---|
API Worker (kenresoft-cms-api by default) |
REST API, auth, cron |
Admin Worker (kenresoft-cms-admin by default) |
Dashboard, static assets only |
D1 database (binding DB) |
Structured data |
| R2 bucket | Media |
| Rate limiting bindings | Auth, forms, public content, recovery |
Configuration lives in the root wrangler.toml. Worker, D1 and R2 names are per-account: if a default name is taken, setup asks for another one.
Ways to deploy
Section titled “Ways to deploy”pnpm run setup: the guided CLI. Recommended.- Manual
wrangler deploy: possible without CI; see the repository’sdocs/DEPLOYMENT.md. - GitHub Actions:
.github/workflows/deploy.ymlis opt-in, gated behind the repository variableDEPLOY_ENABLED == 'true'. - Deploy to Cloudflare button: available for the API Worker in the repository README. Its full-flow behavior is less proven than
setup; prefersetup.
Backups
Section titled “Backups”D1 has 30-day point-in-time recovery (Time Travel) with no setup. R2 has no equivalent; back up media separately. Details are in the repository’s docs/DEPLOYMENT.md, “Backups and recovery”.