Docs/Deployment
Deployment

CLI: Deploy Frontend Pages

Deploy apps/web and apps/admin to Cloudflare Pages using wrangler or Pages CLI.

Last updated Mar 19, 2026

Deploy the core frontend apps only: apps/web and apps/admin.

1. Create Pages projects first

In Cloudflare Dashboard → Workers & Pages:

  1. Create a Pages project for web
  2. Create a Pages project for admin

Keep the names web and admin to match environment variables and docs.

2. Deploy apps/web

apps/web uses Astro with @astrojs/cloudflare and deploys as a Worker with static assets.

cd apps/web
pnpm run build
npx wrangler deploy
cd ../..

Or if the project uses wrangler.toml with a name that maps to a Pages project, follow the project's deploy script.

3. Deploy apps/admin

apps/admin uses Nuxt. Build and deploy to Cloudflare Pages:

cd apps/admin
pnpm run build
npx wrangler pages deploy .output/public --project-name=admin
cd ../..

Or use the project's configured deploy command (e.g. pnpm run deploy if defined).

4. Set environment variables

After deployment, configure Pages environment variables in Cloudflare Dashboard:

  • Backend service URLs (e.g. AUTH_SERVICE_URL, SUPPORT_SERVICE_URL, etc.)
  • app_key (use demo for first run)
  • Any other required public vars

5. SESSION binding warning

If you see a SESSION binding warning, the expected KV binding may not be configured. Check:

  • Wrangler/Pages binding configuration
  • Whether the target environment matches what you prepared

6. Checklist

  • [ ] Both Pages projects exist
  • [ ] apps/web deployed
  • [ ] apps/admin deployed
  • [ ] Critical environment variables set