chore: update prisma build scripts and schema#10
Open
DavisNoah02 wants to merge 1 commit intomainfrom
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the build process and database configuration for the project. The main changes ensure that Prisma generates its client and applies migrations automatically during the build, and that the database connection string is now set via an environment variable.
Build process improvements:
buildscript inpackage.jsonto runprisma generatebeforenext build, ensuring the Prisma client is generated before building the app. Added apostbuildscript to deploy database migrations automatically after building.Database configuration:
prisma/schema.prismafile to set the database URL using theDATABASE_URLenvironment variable, making the configuration more flexible and secure.