Back to Registry

Cloudflare Rehearsal Result — Brand Radar (Preview Deploy)

Summary

The Cloudflare preview deploy rehearsal for Brand Radar is successful.

• Initial direct wrangler deploy --dry-run failed before setup (expected) because the app was not configured for Cloudflare Next.js adapter.
• We then followed the OpenNext Cloudflare setup flow and re-ran preview/deploy.
• Deploy completed successfully to Workers and returned HTTP 200 on the root route.

Environment

• App path: /Users/mattsartori/.openclaw/workspace/elon/projects/brand-radar/temp/app
• Runtime target: Cloudflare Workers via OpenNext
• Wrangler auth: confirmed earlier via wrangler whoami

What Was Changed (for rehearsal)

1. Installed adapter + Wrangler dev dependencies:
   • @opennextjs/cloudflare
   • wrangler
2. Ran migration bootstrap:
   • npx @opennextjs/cloudflare migrate
3. Migration generated/updated:
   • wrangler.jsonc
   • open-next.config.ts
   • .dev.vars
   • public/_headers
   • package.json scripts (preview, deploy, upload, cf-typegen)
   • .gitignore
   • next.config.mjs (needed cleanup after auto-edit)
4. Fixed next.config.mjs to valid ESM form with:
   • initOpenNextCloudflareForDev() import + call

Verification Evidence

1) Local Workers-runtime preview

• Command: npm run preview
• Result: OpenNext build successful; Wrangler local server ready at http://localhost:8787

2) Cloudflare deploy

• Command: npm run deploy
• Result: success
• Worker URL:
  • https://brand-radar.cold-base-47b2.workers.dev
• Version ID:
  • 2092910c-9eae-4a95-a6c8-10c68d6cd2e8

3) HTTP validation

• curl -I to worker URL returned HTTP/2 200
• Body fetch returned status 200
• Response header includes x-opennext: 1

Observed Warnings (non-blocking)

• Prisma warning: package.json#prisma deprecation (future Prisma 7 migration item)
• Next warning: middleware file convention deprecation (middleware -> proxy)
• Bundler warnings about === -0 comparison in generated chunks

Remaining Gaps Before Production Cutover

1. Caching is not fully configured (OpenNext migration warned to set up cache manually)
2. No traffic splitting/canary policy configured yet
3. No formal baseline-vs-Cloudflare latency comparison captured yet
4. Secrets/environment parity needs explicit review for full prod behavior
5. Need security pass against new edge surface before traffic shift

Recommended Next Step

Run a 24-hour canary checklist from:

• reports/cloudflare-migration-rehearsal-checklist.md

Start at 5% traffic (or internal-only audience) and collect p50/p95 latency, error rate, and core workflow timing against Vercel baseline.