Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Vercel deployment instructions #6299

Closed
lnikell opened this issue Sep 28, 2024 · 2 comments · Fixed by #6310
Closed

Missing Vercel deployment instructions #6299

lnikell opened this issue Sep 28, 2024 · 2 comments · Fixed by #6310
Labels
docs Documentation creation, updates or corrections

Comments

@lnikell
Copy link

lnikell commented Sep 28, 2024

Hi, and thank you for the great work on Prisma ORM. After reading the docs, I noticed that this page does not have complete information. It does not explain how the database structure from your codebase will appear on Vercel.

It does not specify the need for a separate CI/CD flow for running migrations or using a vercel-build script in package.json with.

"vercel-build": "prisma generate && prisma migrate deploy && next build",
@lnikell lnikell added the docs Documentation creation, updates or corrections label Sep 28, 2024
@jharrell
Copy link
Member

jharrell commented Oct 1, 2024

@lnikell thanks for the info! Did the provided instructions not work? We have recommended the postinstall script so far.

@nikolasburk
Copy link
Member

I went ahead and expanded the docs according to my understanding of your request @lnikell in this PR: #6310

If I understood correctly, the main point you made was about a more advanced CI/CD scenario where not only Prisma Client needs to be generated but you also want to update the DB schema in the build pipeline, is that correct? Does the PR address your concern?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation creation, updates or corrections
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants