Step 8: Deploy (Cloudflare or Vercel)

Build your siteStep 8 of 9

1. ✓
2. ✓
3. ✓
4. ✓
5. ✓
6. ✓
7. ✓
8. 8Deploy (Cloudflare or Vercel)
9. 9

Now you'll put the site live. Pick one host: Option A is Cloudflare, Option B is Vercel.

Before you start

• Step 7 finished
• A Cloudflare account
• Your repo on GitHub or GitLab

Do it

Type each command on its own and wait for it to finish before the next one.

Option A: Cloudflare Workers

Open wrangler.jsonc and set your Worker's name:

"name": "my-site"

Check the deploy locally. This does not need a login.

npx wrangler deploy --dry-run

Expected output

Read 52 files from the assets directory ./site/.vitepress/dist
No bindings found.
--dry-run: exiting now.

If you see an error: assets directory does not exist means you have not built yet. Run npm run build first.

Commit and push your project.

git add -A
git commit -m "My site"

Expected output

[main 1a2b3c4] My site

git push

Expected output

To github.com:you/my-site.git
   main -> main

Requires: Cloudflare login (in the browser)

Sign in at dash.cloudflare.com. You connect the repo there, so no token goes in your project.

In Cloudflare, open Workers & Pages → Create → Import a repository. Pick your repo and use these settings:

Setting	Value
Root directory	/
Build command	npm run build
Deploy command	npx wrangler deploy
Node version	from .nvmrc (or variable NODE_VERSION = 22.20.0)

If you see an error: name does not match means the Worker name in Cloudflare differs from "name" in wrangler.jsonc. Make them the same.

Option B: Vercel

Now you'll deploy the same site to Vercel instead. The starter already has a vercel.json. It tells Vercel to run npm ci, then npm run build, and serve site/.vitepress/dist.

Requires: Vercel login

The login command opens your browser. Run it on its own and finish the sign-in. No token goes in your project.

npx vercel login

Expected output

> Success! Email authentication complete

If you see an error: command not found: vercel is fine: npx downloads it. If the browser does not open, copy the URL it prints.

Deploy a preview first. Answer the questions; the defaults are correct.

npx vercel

Expected output

🔗  Linked to you/my-site
✅  Preview: https://my-site-abc123.vercel.app

When the preview looks right, deploy to production.

npx vercel --prod

Expected output

✅  Production: https://my-site.vercel.app

If you see an error: Error: No Output Directory named "dist" means vercel.json is missing. Copy it from the starter and run the command again.

Prefer no CLI? In the Vercel dashboard choose Add New → Project, import your repo, and keep the settings from vercel.json.

Result

Your host builds on every push to main. The site is live at my-site.<your-subdomain>.workers.dev (Cloudflare) or my-site.vercel.app (Vercel).

Checkpoint

• The live URL loads
• Cloudflare: the Worker name matches wrangler.jsonc
• Vercel: the production URL loads

Next step

Step 9: Custom domain

Back: Step 7: Test 2–3 rounds