# Next.js + MySQL This is a [Next.js](https://nextjs.org/) project that uses [Prisma](https://www.prisma.io/) to connect to a [PlanetScale](https://planetscale.com/) MySQL database and [Tailwind CSS](https://tailwindcss.com/) for styling. ## Demo https://next-mysql.vercel.app ## Prerequisites - [Node.js](https://nodejs.org/en/download/) - [PlanetScale CLI](https://github.com/planetscale/cli) - Authenticate the CLI with the following command: ```sh pscale auth login ``` ## Set up the database Create a new database with the following command: ```sh pscale database create ``` > A branch, `main`, was automatically created when you created your database, so you can use that for `BRANCH_NAME` in the steps below. ## Set up the starter Next.js app Execute [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app) with [npm](https://docs.npmjs.com/cli/init), [Yarn](https://yarnpkg.com/lang/en/docs/cli/create/), or [pnpm](https://pnpm.io) to bootstrap the example: ```bash npx create-next-app --example with-mysql nextjs-mysql # or yarn create next-app --example with-mysql nextjs-mysql # or pnpm create next-app --example with-mysql nextjs-mysql ``` Next, you'll need to create a database username and password through the CLI to connect to your application. If you'd prefer to use the dashboard for this step, you can find those instructions in the [Connection Strings documentation](https://docs.planetscale.com/concepts/connection-strings#creating-a-password) and then come back here to finish setup. First, create your `.env` file by renaming the `.env.example` file to `.env`: ```sh mv .env.example .env ``` Next, using the PlanetScale CLI, create a new username and password for the branch of your database: ```sh pscale password create ``` > The `PASSWORD_NAME` value represents the name of the username and password being generated. You can have multiple credentials for a branch, so this gives you a way to categorize them. To manage your passwords in the dashboard, go to your database overview page, click "Settings", and then click "Passwords". Take note of the values returned to you, as you won't be able to see this password again. ```text Password production-password was successfully created. Please save the values below as they will not be shown again NAME USERNAME ACCESS HOST URL ROLE PLAIN TEXT --------------------- -------------- ----------------------------------- ------------------ ------------------------------------------------------- production-password xxxxxxxxxxxxx xxxxxx.us-east-2.psdb.cloud Can Read & Write pscale_pw_xxxxxxx ``` You'll use these properties to construct your connection string, which will be the value for `DATABASE_URL` in your `.env` file. Update the `DATABASE_URL` property with your connection string in the following format: ```text mysql://:@/?sslaccept=strict ``` Push the database schema to your PlanetScale database using Prisma. `npx prisma db push` Run the seed script to populate your database with `Product` and `Category` data. `npm run seed` ## Run the App Run the app with following command: `npm run dev` Open your browser at [localhost:3000](localhost:3000) to see the running application. ## Deploy your own After you've got your application running locally, it's time to deploy it. To do so, you'll need to promote your database branch (`main` by default) to be the production branch ([read the branching documentation for more information](https://docs.planetscale.com/concepts/branching)). ```sh pscale branch promote ``` Now that your branch has been promoted to production, you can either use the existing password you generated earlier for running locally or create a new password. Regardless, you'll need a password in the deployment steps below. Deploy the example using [Vercel](https://vercel.com?utm_source=github&utm_medium=readme&utm_campaign=next-example): [![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/vercel/next.js/tree/canary/examples/with-mysql&project-name=with-mysql&repository-name=with-mysql&env=DATABASE_URL) > Make sure to update the `DATABASE_URL` variable during this setup process.