Setting up your project

Deploy for the first time

1. 1Cloudflare's tool (Wrangler) needs Node.js 22 or newer. Check with node -v; if you are on an older version, install the current LTS from nodejs.org or with nvm install 22.
2. 2Create an account at dash.cloudflare.com. No card needed for the free plan.
3. 3In the project folder run npx wrangler login. A browser window asks you to allow Wrangler; approve it and come back to the terminal.
4. 4Optional but recommended: run npm run preview to build and run the site locally exactly as it will run on Cloudflare. Open the printed URL, click around, then stop it with Ctrl+C.
5. 5Run npm run deploy. The first time, Wrangler asks to create the Worker. When it finishes it prints a URL ending in .workers.dev. Open it: your site is live.

Every later deploy is the same single command. Deploys take about a minute and are atomic: visitors never see a half-updated site.

Set your production keys

1. 1Run npm run cf:secrets. It reads .env.local and pushes every value to Cloudflare as a Worker secret, the public NEXT_PUBLIC_ ones included: your deployed site reads them at request time, and Cloudflare only knows what you have pushed. Re-run it whenever you change a value.
2. 2Public values also need to be in .env.local when you run npm run deploy, because the browser side of the site gets them inlined at build time. Keep the file filled in and both sides agree.
3. 3You can also see and edit them in the dashboard: Workers & Pages → your Worker → Settings → Variables and Secrets.

Static sites have no server-side values, so this step does not apply to them.

Deploy from CI (optional)

1. 1Create an API token at My Profile → API Tokens → Create Token → Create Custom Token with exactly these permissions, each an Account row, scoped to your account: Workers Scripts · Edit, Account Settings · Read. Nothing else is needed for npm run deploy.
2. 2In your CI, set CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID (the account id is on the dashboard's overview page), then run npm ci and npm run deploy. Wrangler uses the token instead of a browser login.

These are the same permissions BytesJoy's own weekly check deploys with, so they are known to be sufficient.

Use your own domain

1. 1Buy a domain in Cloudflare → Domain Registration (at-cost pricing), or add one you already own with Add a domain and switch its nameservers to the two Cloudflare gives you at your current registrar. Nameserver changes take minutes to a day.
2. 2Open Workers & Pages → your Worker → Settings → Domains & Routes → Add → Custom domain, and enter yourdomain.com. Cloudflare creates the DNS record and certificate for you. Add www.yourdomain.com the same way if you want both.
3. 3Visit the domain. HTTPS works automatically.

Update the other providers for production

1. 1Supabase: under Authentication → URL configuration, set the Site URL to https://yourdomain.com and add https://yourdomain.com/auth/callback to Redirect URLs.
2. 2Resend: the sending domain you verified should be this domain or a subdomain of it. If your DNS is on Cloudflare now, add the Resend DNS records under DNS → Records.
3. 3If you changed any NEXT_PUBLIC_ value, run npm run deploy again so it is rebuilt in.