Since Vercel uses a specific linux distribution we need to make sure to edit our connection string to point to the correct certificate location, which is /etc/pki/tls/certs/ca-bundle.crt. Using the connection string details you saved earlier for our main branch, create a new environment variable for our DATABASE_URL with the connection string you saved earlier. Once you have committed your files to Github, select the new project option on Vercel, and scroll down to the environment variables section. Since we are deploying to Vercel, make sure that you are signed up and have your Github account connected to it. Now, if we visit we should see our Post record fetched from our PlanetScale database! Deploying Import prisma from "././lib/prisma" export default async function assetHandler ( req, res ) Go ahead and login to the PlanetScale CLI by issuing the following command in your terminal of choice: This can be done easily with the PlanetScale CLI. Since Prisma migrations follow PlanetScales non-blocking schema migration workflow, we will need to create two additional branches off of our main database branch in order to handle these schema changes. These are the details we will be using in our Prisma DATABASE_URL environment variable on Vercel during deployment.
PRISMA APP ON KOPLAYER PASSWORD
(You can always generate a new password if you misplace these credentials, and delete the misplaced one). Using the dropdown, select the Prisma format and make sure to save these connection details safely somewhere, as PlanetScale hides your password after the initial generation. Now that we have our database setup with the copy Prisma migration data option enabled, go ahead and click on the connect button in the top right of your dashboard and generate a new password for your main branch. In my case, both my Vercel application and PlanetScale database will be in the Western U.S.Įxcellent! Once your database is created, head over to the settings page and enable Automatically copy migration data which will store our Prisma schema migrations in a table called _prisma_migrations any time we merge a deploy request.Īwesome! Head back to your databases dashboard and you should see this view. In a serverless application, it's important to select a database region that is as close as possible to where your application is being deployed in order to reduce latency.
PRISMA APP ON KOPLAYER DOWNLOAD
Once you're all signed up, download the PlanetScale CLI which will be important for connecting to our database locally, creating new database branches, and issuing deploy requests when we make changes to our schema using Prisma.įrom your dashboard, click on the "Create database" button and enter a database name (I'll name mine tutorial-db), select a region, and deselect the launch tutorial database option.
Setup PlanetScaleīefore we begin, go ahead and sign up for an account at PlanetScale.
PRISMA APP ON KOPLAYER HOW TO
In this article, we'll go over how to create a brand new Next.js Prisma application, connect it to PlanetScale using their newly released connection string options, issue a simple deploy request using PlanetScales non-blocking schema change workflow, and then deploy it to production using Vercel.
PlanetScale have also introduced some really cool concepts like database branches (similar to Git branching logic) so your database migrations are seamless and non-blocking. Vitess is the same technology that powers many hyperscale websites that require critical uptime, performance and scalability. Based on Vitess, PlanetScale is a new DBaaS platform that allows you to spin up a database in seconds, without having to worry at all about connection management.
0 kommentar(er)
