-
Notifications
You must be signed in to change notification settings - Fork 9
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
Use SQLite in dev and Postgres in prod #16
Comments
@iamshanvy wanna take a crack at this? 👀 |
where current postgres db is hosted? to avoid dealing with different dbs turso could be used to host sqlite for the demo, free tier will be enough here, might be simpler solution? |
Currently hosted on vercel postgres and it's part of our plan so the cost is negligible. ITYJ (I trust your judgment) postgres or SQLite - whatever works, turso free tier could work but I wasn't able to set it up previously with turso super quick and gave up in favour of postgres - now I see this could be more overhead. Your call honestly if you're interested in taking this on, if not - no worries, no pressure 🧘 - can take a crack at it this weekend or colab on Gather (island.rubric.sh) any time. 🫡 |
okie, I will look into this on Friday/Saturday this week if that's good, new Open AI toys created me a bunch of work till then 😂 |
making turso work is surprisingly not straightforward 😂 I will spend some more time tomorrow, otherwise postgres it is, will update here |
uh oh |
honestly man, I heard it pitched as "sqlite in prod" |
Closed by #21 Awesome work @iamshanvy 🎉 |
Decoupled from #9
Some context:
Possible solution:
provider="sqlite"
in the local schema andprovider="postgres"
in prod schemaprisma generate
andprisma db push
on the right schema depending on env. This could be done in bash in package.json withNODE_ENV
or we could just override the build command in Vercel (or any hosting platform) toprisma generate --schema=./prisma/local.prisma.schema
The text was updated successfully, but these errors were encountered: