How D1 work with Drizzle ORM?

I created a svelte repo using create cloudflare cli.

I found

import { defineConfig } from 'drizzle-kit';
if (!process.env.DATABASE_URL) throw new Error('DATABASE_URL is not set');

export default defineConfig({
    schema: './src/lib/server/db/schema.ts',

    dbCredentials: {
        url: process.env.DATABASE_URL
    },

    verbose: true,
    strict: true,
    dialect: 'sqlite'
});

import { defineConfig } from 'drizzle-kit';
if (!process.env.DATABASE_URL) throw new Error('DATABASE_URL is not set');

export default defineConfig({
    schema: './src/lib/server/db/schema.ts',

    dbCredentials: {
        url: process.env.DATABASE_URL
    },

    verbose: true,
    strict: true,
    dialect: 'sqlite'
});

for the drizzle config. Isn't only for local sqlite db, isn't? How can I config for production D1 database? I know I have to configure D1 in wrangler file. But there is no need to configure d1 database inside drizzle config file? How about generate and migrate?

sithuOP•2/11/25, 12:56 AM

I mean like this in config file:

export default defineConfig({
  out: `./src/lib/server/db/migrations`,
  schema: "./src/lib/server/db/schemas",
  dialect: "sqlite",
  driver: "d1-http",
  dbCredentials: {
    accountId: process.env.CLOUDFLARE_ACCOUNT_ID!,
    databaseId: process.env.CLOUDFLARE_DATABASE_ID!,
    token: process.env.CLOUDFLARE_TOKEN!
  },
  verbose: true,
  strict: true
});

export default defineConfig({
  out: `./src/lib/server/db/migrations`,
  schema: "./src/lib/server/db/schemas",
  dialect: "sqlite",
  driver: "d1-http",
  dbCredentials: {
    accountId: process.env.CLOUDFLARE_ACCOUNT_ID!,
    databaseId: process.env.CLOUDFLARE_DATABASE_ID!,
    token: process.env.CLOUDFLARE_TOKEN!
  },
  verbose: true,
  strict: true
});

sithuOP•2/11/25, 12:56 AM

How can I keep both sqlite and d1 inside one config file?

Hurby•2/11/25, 6:47 AM

@Sithu Khant https://orm.drizzle.team/docs/connect-cloudflare-d1

HHurby @Sithu Khant <https://orm.drizzle.team/docs/connect-cloudflare-d1>

sithuOP•2/11/25, 7:23 AM

yeah, I saw that.

sithuOP•2/11/25, 7:24 AM

I found Drizzle orm doesn't have option to handle both dev and prod database at the same time, we have to manually configure ourself.

sithuOP•2/11/25, 7:32 AM

So, this is what I did (maybe to someone who is looking for):

import "dotenv/config";
import { defineConfig } from "drizzle-kit";

const isProd = process.env.NODE_ENV === "production";

export default defineConfig({
  out: `./src/lib/server/db/migrations-${isProd ? "prod" : "dev"}`,
  schema: "./src/lib/server/db/schemas",
  dialect: "sqlite",
  driver: "d1-http",
  dbCredentials: {
    accountId: process.env.CLOUDFLARE_ACCOUNT_ID!,
    databaseId: isProd
      ? process.env.CLOUDFLARE_DATABASE_ID!
      : process.env.CLOUDFLARE_DEV_DATABASE_ID!,
    token: process.env.CLOUDFLARE_TOKEN!
  },
  verbose: true,
  strict: true
});

import "dotenv/config";
import { defineConfig } from "drizzle-kit";

const isProd = process.env.NODE_ENV === "production";

export default defineConfig({
  out: `./src/lib/server/db/migrations-${isProd ? "prod" : "dev"}`,
  schema: "./src/lib/server/db/schemas",
  dialect: "sqlite",
  driver: "d1-http",
  dbCredentials: {
    accountId: process.env.CLOUDFLARE_ACCOUNT_ID!,
    databaseId: isProd
      ? process.env.CLOUDFLARE_DATABASE_ID!
      : process.env.CLOUDFLARE_DEV_DATABASE_ID!,
    token: process.env.CLOUDFLARE_TOKEN!
  },
  verbose: true,
  strict: true
});

in my package.json file:

    "db:generate": "cross-env NODE_ENV=development drizzle-kit generate",
    "db:migrate": "cross-env NODE_ENV=development drizzle-kit migrate",
    "db:studio": "cross-env NODE_ENV=development drizzle-kit studio",
    "db:generate:prod": "cross-env NODE_ENV=production drizzle-kit generate",
    "db:migrate:prod": "cross-env NODE_ENV=production drizzle-kit migrate",
    "db:studio:prod": "cross-env NODE_ENV=production drizzle-kit studio"

    "db:generate": "cross-env NODE_ENV=development drizzle-kit generate",
    "db:migrate": "cross-env NODE_ENV=development drizzle-kit migrate",
    "db:studio": "cross-env NODE_ENV=development drizzle-kit studio",
    "db:generate:prod": "cross-env NODE_ENV=production drizzle-kit generate",
    "db:migrate:prod": "cross-env NODE_ENV=production drizzle-kit migrate",
    "db:studio:prod": "cross-env NODE_ENV=production drizzle-kit studio"

you have to install

cross-env

cross-env

package:

npm i -D cross-env

npm i -D cross-env

sithuOP•2/11/25, 7:34 AM

I chose to use d1 for both dev and prod, so I would get realtime production database features.

Brett (Fiberplane)•2/11/25, 9:18 AM

to throw another example in the mix here, this is what we do for our template Hono app with Drizzle + D1: https://github.com/fiberplane/create-honc-app/blob/main/templates/d1/drizzle.config.ts

it's a little less elegant, does a manual search for the local D1 database in

.wrangler

.wrangler

to find the correct file. which makes our migration scripts look like this:

    "db:migrate": "wrangler d1 migrations apply honc-d1-database --local",
    "db:migrate:prod": "ENVIRONMENT=production drizzle-kit migrate",

    "db:migrate": "wrangler d1 migrations apply honc-d1-database --local",
    "db:migrate:prod": "ENVIRONMENT=production drizzle-kit migrate",

then we rely on having separate

.dev.vars

.dev.vars

and

.prod.vars

.prod.vars

files.

i gotta say, i rather like your solution @Sithu Khant – might end up updating our templates to use something like yours instead

GitHub

create-honc-app/templates/d1/drizzle.config.ts at main · fiberplane...

Template for setting up a new HONC stack project. Contribute to fiberplane/create-honc-app development by creating an account on GitHub.

BBrett (Fiberplane)to throw another example in the mix here, this is what we do for our template Ho...

sithuOP•2/11/25, 9:59 AM

hey, I am glad that my method isn't wired, I thought it is wired and not the ideal way to do so. But I am now confident enough!

sithuOP•2/11/25, 10:01 AM

btw, I just found one of your work colleagues shared about your works on hono server showcase channel. That is awesome!

Brett (Fiberplane)•2/12/25, 10:16 AM

okay yeah one of my colleagues double checked bc i didn't have time to work on the templates this week — for note: our template handles a local D1 if you're interested in that. my colleague pointed out that your setup has a remote Dev database and a remote Prod database. still a nice solution you found, definitely seems like it works best for that case