1. Node.js >=v20.11.0
2. pnpm >=v9.15.1

1. Create a production D1 database.

2. The starter kit focuses on 2 environments, development on local machine and production on remote machine. So, create the following files:

   1. .env.development: duplicate .env.example, and set the variables to development values.
   2. .env.production: duplicate .env.example, and set the variables to production values.
   3. wrangler.toml.development: duplicate wrangler.toml.example, and set the variables to development values.
   4. wrangler.toml.production: duplicate wrangler.toml.example, and set the variables to production values.

3. Install the app's dependencies:

pnpm install

4. Generate db migration files (that documents schema changes in an SQL script).

pnpm db:generate

5. Run db migrations (that executes the SQL script to update the database to match the schema).

• dev (local) db: pnpm db:migrate:dev
• prod (remote) db: pnpm db:migrate:prod

6. View the database using a graphical user interface:

• dev (local) db: pnpm db:studio:dev
• prod (remote) db: pnpm db:studio:prod

• Run Next.js on dev. Ideal for development since it supports hot-reload/fast refresh.

pnpm dev

⚠️ Warning: next start will return an error due to how the application is designed to run on Cloudflare pages.

• Run Cloudflare Pages locally. Ideal to test how the app would work after being deployed.

pnpm pages:dev

⚠️ Warning #1: Connecting to the prod remote db on the local code is not supported.

⚠️ Warning #2: All pages deployed to Cloudflare Pages run on edge runtime, whereas ISR only works on Nodejs runtime (because how Vercel designed their functions); so, some functions like revalidatePath will throw an error when running the app with pnpm pages:dev. But, the functions work as expected after deploying.

• Deploy code to pages:

pnpm pages:deploy