04. Deploy Frontend Pages

With the backend in place, the next step is getting the frontend online.

1. Create the two Pages projects first

Create the frontend Pages projects before the first real frontend deployment.

Keep the names aligned with the repository defaults.

This avoids confusion in environment variables, docs, and deployment scripts.

The public site is usually the first frontend app you want online.

Deploy it from the apps/web directory and keep the first deployment simple.

The frontend deployment command is normally scoped to the app directory so that:

Do not try to collapse everything into one custom command before the default deployment works.

On the first pass, make sure apps/web at least points to:

Start with the repository defaults if needed, verify the whole system works, then customize.

After web, deploy apps/admin.

The admin is required for initialization and ongoing management, so it should be online immediately after the public site.

For the first pass, apps/admin often works with fewer additional environment variables than web.

Still, you should verify:

You may see a warning about an invalid SESSION binding during build or deployment.

That warning usually means the expected Cloudflare KV binding has not been configured yet in the target environment.

Do not ignore it blindly.

Check:

Before moving on, confirm:

Once those are done, you can move on to domains and production URLs.