3 ms·

This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon back

This looks great. Question specifically on the Cloudflare Workers target: when you deploy there, does Typebase use D1 for the DB, or does the Postgres/Neon backend stay the same regardless of which server target you pick (Vercel/Workers/Deno) - i.e. is the DB layer decoupled from the server runtime, or does choosing Workers also mean choosing D1? I ask because I've shipped a small Workers+D1 service and the main friction I've hit isn't the server code, it's Workers' constraints around D1 (no long-running connections, HTTP-based driver quirks) - curious whether Typebase abstracts that away or whether you still feel it at the DB layer when targeting Workers specifically.

optimisticedits 1mo ago
I see no code there to automatically pick D1 for the DB when you deploy to Cloudflare. On Cloudflare, it should use the `@neondatabase/serverless` driver configured here https://github.com/typebase-io/monorepo/blob/fa3af0b71126caa4c3158256fdf329adbe2ca8a6/apps/cli/src/helpers/constants.ts#L30 https://github.com/typebase-io/monorepo/blob/fa3af0b71126caa...
- SifatAhmed 1mo ago
  [flagged]
- andrewww-dev 1mo ago
  Hey! For now we only support Neon but the idea is too add more DB providers soon. I wanted to build a "base layer" to show that Typebase is versatile enough, I'll add D1 to the priorities
  - SifatAhmed 1mo ago
    [dead]