In Part 1 we built an edge-native headless CMS on Workers with D1 + R2. Deploying SonicJS is not the...
In Part 1 we built an edge-native headless CMS on Workers with D1 + R2. Deploying SonicJS is not the hard part — doing it safely on every push is.
This post covers production bindings, secrets, migrate-before-deploy, and a GitHub Actions workflow that typechecks, migrates D1, deploys the Worker, and smoke-checks /health.
Prerequisites
A SonicJS project that already runs locally with wrangler dev
Cloudflare account + Wrangler logged in once (npx wrangler login)
Most headless CMS setups still look like 2018: a Node server, a Postgres box in one region, and S3...
You deployed the CMS (Part 2). Health checks pass. Then someone tries to log in and you get one...
Part 1 was the foundation - Jenkins as a Code, ephemeral workers, the whole thing. Part 2 was the...
A Deploy to Cloudflare button turned my local-dev config into production secrets, and shipped copies of my app with admin auth…
A complete guide to deploying a Next.js application to AWS using GitHub Actions CI/CD pipelines. Covers EC2, Nginx, PM2,…
A suite that only runs on your laptop protects only your laptop. This chapter wires the whole thing...
