Run the prisma migrations programatically #549
Merged
Conversation
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.
Description
Closes #290
The prisma binary is 200MB large and we only need it to execute migrations. As prisma is aimed at enterprise grade deployments with CI/CD pipelines for executing migrations etc., there is no user friendly way to run migrations from a self contained app aimed at self hosted usage: prisma/prisma#28904
As such I copied and slightly tweaked the workaround from the above issue, kudos to @lr-harm !!
The image size reduction is on the order of 200 MB with Next+Prisma client remaining massive. I attempted migrating to the no-Rust Prisma client, but got some weird build errors and decided to skip it for now.