Setup

Prerequisites

In the site folder, make sure these commands succeed.

npm install
npm exec riebeckite build

A successful build creates dist/.

my-site/
├─ app/
├─ content/
├─ dist/               ← publish this
├─ riebeckite.config.ts
└─ package.json

Cloudflare Workers serves the files from dist/. Build-time state such as .riebeckite/ and plugin caches is not published.

Incremental processing happens during riebeckite build on your machine or GitHub Actions runner. Wrangler then uploads the newly generated dist/ as Workers Static Assets; Workers do not perform incremental builds. The generated GitHub Actions workflow persists .riebeckite/cache and .riebeckite/build/content-state.json for this build step, never dist/.

1. Create a Cloudflare account

Create an account at cloudflare.com. The free plan is enough to get started.

2. Get wrangler

A site generated with create-riebeckite's Cloudflare Workers choice already includes the Wrangler dependency and wrangler.jsonc, so no extra install or setup is needed.

For a site generated with Not now, or when preparing one manually, run this in the site folder:

npm install -D wrangler

wrangler is the official command-line tool for deploying to Cloudflare Workers.

3. Add wrangler.jsonc

npm exec -- riebeckite publish run --execute creates wrangler.jsonc from the site folder name when the file is missing, so this step is only needed when you want to review or customize it. To create it yourself, add a wrangler.jsonc in the site root:

my-site/
|- dist/
|- package.json
|- riebeckite.config.ts
`- wrangler.jsonc

Change name first.

{
  "name": "my-riebeckite-site",
  "assets": {
    "directory": "./dist"
  }
}

name is the Worker name on Cloudflare. Choose a name that is unique to you. Keep assets.directory as ./dist.

This maps to:

Riebeckite
    ↓
generates dist/
    ↓
Wrangler
    ↓
publishes dist/ as Static Assets

4. Log in to Cloudflare

riebeckite publish run --execute opens the browser and asks you to log in on the first run. To log in ahead of time, or if you run Wrangler directly, use:

npx wrangler login

A browser window opens. Log in to Cloudflare and grant access.

5. Deploy

npm exec -- riebeckite publish run --execute

riebeckite publish run --execute calls Wrangler to publish dist/. It logs you in first when needed and creates wrangler.jsonc when it is missing. Choosing Cloudflare Workers in create-riebeckite and answering Yes to Deploy now? runs this build and deploy immediately after scaffolding. To run Wrangler directly instead, use npx wrangler deploy.

flowchart TD
    Build["npm exec riebeckite build"]
    Dist["dist/"]
    Deploy["npm exec -- riebeckite publish run --execute"]
    Workers["Cloudflare Workers"]
 
    Build --> Dist
    Dist --> Deploy
    Deploy --> Workers

The deploy prints a URL such as https://<name>.<account>.workers.dev. Open it in a browser. If the site loads, deployment worked.

6. Match baseUrl to the deployed URL

After the first successful deploy, update baseUrl in riebeckite.config.ts.

site: {
  baseUrl: "https://my-riebeckite-site.example.workers.dev",
},

Then build and deploy again.

npm exec riebeckite build
npm exec -- riebeckite publish run --execute

This makes sitemap and feed URLs match the public site.

In other words, the first publish follows this flow:

flowchart TD
    FirstBuild["1. Build"]
    FirstDeploy["2. First deploy"]
    URL["3. Note the public URL"]
    BaseUrl["4. Set baseUrl"]
    SecondBuild["5. Rebuild"]
    SecondDeploy["6. Redeploy"]
 
    FirstBuild --> FirstDeploy
    FirstDeploy --> URL
    URL --> BaseUrl
    BaseUrl --> SecondBuild
    SecondBuild --> SecondDeploy

7. Check before publishing

You can verify the Cloudflare Workers configuration without deploying.

Dry run

npx wrangler deploy --dry-run

This checks the deployment preparation without actually publishing. Use it when you do not want to go live yet but want to confirm the Wrangler configuration.

Wrangler dev

npx wrangler dev

This serves a local version close to the deployed Worker. A simple way to think about it:

Day-to-day article and site development
  → riebeckite dev
 
Check the Cloudflare serving state
  → wrangler dev
 
Publish for real
  → riebeckite publish run --execute