Cloudflare hosting

Make the roadmap reachable anywhere.

Recommendation

Deploy the current app as a Cloudflare Pages static site first. Move to OpenNext on Workers only when the app needs server behavior.

Static

today

Pages

host

Workers

later

Recommended for this app today

Use now: Cloudflare Pages static site

The current app is strategy pages, assets, and static routes. Exporting to static files gives you a fast public URL with the least deployment complexity.

Upgrade path

Use later: OpenNext on Cloudflare Workers

If this becomes a real logged-in app with server behavior, API routes, middleware, or dynamic rendering, use the Cloudflare adapter for OpenNext and deploy through Wrangler.

Too much surface area

Avoid for now: custom infrastructure

There is no database, queue, auth, or background job yet. Keep hosting boring until the product needs those capabilities.

Deploy path

Four steps from localhost to phone.

This page separates the decision from the execution. Static Pages hosting is the fastest way to make the planning app accessible on the go, while keeping the repo ready for a Workers upgrade later.

Deployment step

Prepare the static export

Add a static export setting to Next config only if you are ready to deploy this as a purely static site.

Command / setting

output: 'export'

Deployment step

Build the production files

Run the normal Next build. With static export enabled, the deployable files land in the output folder.

Command / setting

npm run build

Deployment step

Verify Cloudflare auth

Wrangler needs to know which Cloudflare account to deploy into before it can publish the site.

Command / setting

npx wrangler whoami

Deployment step

Publish to Pages

Deploy the static output folder to a Cloudflare Pages project and use the generated pages.dev URL on your phone.

Command / setting

npx wrangler pages deploy out --project-name codex-currently

Readiness checklist

No private keys or local-only screenshots are required at runtime.

All pages render through static App Router routes.

The channel assets and thumbnails are committed or included in the deployment source.

The public URL works on mobile data, not only on localhost.

The deployment path is documented before adding dynamic app features.

Move to Workers when

You add authenticated Skool/member dashboards.

You need API routes, server actions, or dynamic data at request time.

You want Cloudflare bindings like R2, D1, KV, Queues, or Workers AI.

You need a preview that behaves like the Cloudflare Worker runtime.

Operating note

Hosting is a distribution tool, not the product.

Use it daily

Open the public URL from your phone while recording, planning, or reviewing the channel.

Keep commands visible

The deploy commands become their own future Codex Currently tutorial.

Upgrade deliberately

Do not add Workers complexity until the app has a real dynamic workflow.