docs: Add information about how to turn off Prisma/db operations during a Vercel deploy to reduce Postgres Storage use #10294
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.
See: https://discord.com/channels/679514959968993311/1221799675586154577
For Redwood developers using Vercel and their Postgres storage option, the lower Hobby plans have some storage and write limits per month.
By default when redwood deploys, Prisma migrations and data migrations can be called -- which adds some overhead that can eat into those usage limits.
This PR adds a note to show how these options can be turned off during deploys and then folks can run migrations only when needed.
This resolved the user's issue noted above in the Discord chat.