Staging is Dead, Long Live Previews!
summary
Claims that a full‑stack preview workflow is live with Neon and Vercel, creating a database per PR that gets Prisma migrations applied during the Vercel build, populating seeded data and swapping in branch‑specific connection strings as environment variables. Demo shows Next.js app, serverless Postgres branching, and Vercel preview deploys all created automatically, and the new Neon → Vercel integration launches in beta so branches, previews, and isolated compute actually work end to end.
AI-written summary · about
chapters (18)
- 0:00Start
- 3:48Dedicated database for each preview
- 4:11Maintenance nightmare
- 4:42Neon Branching can help recover lost data
- 7:00A look at the app and its initial state
- 7:16The app is backed by a Postgres database already
- 7:31Migrations run as part of the build step
- 8:044. Create a Neon project
- 8:375. Create databases and users
- 9:14Import data into Neon
- 9:45Edit the old environment variables
- 10:05Add the integration to Vercel
- 10:52Check the env variables and branches
- 11:20Set the shadow database url & get the dev env variables
- 12:09Make changes locally
- 12:37Inspect the changes
- 12:58Generate the migrations using Prisma Migrate
- 13:34Commit the changes to GitHub!
related talks
31mInteractive web apps at the Edge with Remix, Neon, and Prisma
49mThe URL that will change testing and QA forever
21mWith Preview Environments, Everyone is Invited To the Party
12mApplication Preview Environments in 5 Minutes
24mCreate Preview Environments for Terraform
27mPlanetScale and Prisma: building in the cloud
34mEnabling data at massive scale with Next.js
16mHow Next.js and Prisma make frontend developers full-stack