You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using drizzle-orm/sqlite-core as the database provider for a turborepo project. In the turborepo project, the following services will need the database for reads and writes:
@turborepo/apps/web
@turborepo/packages/api
@turborepo/packages/auth
@turborepo/packages/core
At the moment, the sqlite db lives in @turborepo/packages/db. It has a set of drizzle commands like generate and migrate, and it has the connection string with the file prefix
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I am using
drizzle-orm/sqlite-core
as the database provider for a turborepo project. In the turborepo project, the following services will need the database for reads and writes:At the moment, the sqlite db lives in @turborepo/packages/db. It has a set of drizzle commands like generate and migrate, and it has the connection string with the file prefix
I am having a hard time deploying the db for the services in docker containers in staging and prod.
how should i rewrite the db? Should it lose the file url and become an http server with a query endpoint?
I am not interested in cloud db as a service like turso, libsql, flyio. I want to self-host
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions