Kenshi:
Hey,
I recently switched to Nuxt-Hub for the simple database implementation and S3 support, but I have run into an issue I can't figure out how to work around. I'm working with Docker to deploy my Nuxt app and build my own Docker images for each one. After building a Nuxt app that's using the Nuxt Hub without setting anything besides the db: 'postgresql', it causes an error to occur on launch Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@electric-sql/pglite' imported from /prod/server/node_modules/drizzle-orm/pglite/driver.js. I tried to follow the documentation and had set the driver to postgres-js but that causes another issue when building the app postinstall: ERROR postgres-js driver requires DATABASE_URL, POSTGRES_URL, or POSTGRESQL_URL environment variable. It is not suitable for me to set the ENV variables on build as the app is being deployed for multiple clients and these change on every Nuxt Instance.
Could you suggest any workaround for this issue? If there are any.
Thanks in advance.

EDIT: I have also tried setting the applyMigrationsDuringBuild to false but nothing changed

NuxtHub needs to know the database env in order to apply the database migrations at build time
Kenshi
—
Yesterday at 8:54 AM
Yeah, I'm aware of that, that's why I tried to disable the migration at build as stated in the docs.
Atinux
—
Yesterday at 8:57 AM
Could you try to set a fake DATABASE_URL for the build to see if it passes?
If you disabled migrations it shouldn’t call the database anyway
Kenshi
—
Yesterday at 8:59 AM
We did try that, but apparently nuxt hub hard codes the variable into the cooked build instead of reading it from the env file
Feels counter intuitive to me but it is what it is
It's for all of the variables as well not only the database
Atinux
—
Yesterday at 10:52 AM
It should be possible to fix this
How do you plan to manage the migrations @kenshi ?
Atinux
—
Yesterday at 11:22 AM
what do you think of this @onmax ?
onmax
—
Yesterday at 1:09 PM
Connection URL gets hardcoded into generated hub/db.mjs at build time via JSON.stringify(connection). Cloudflare deployments (D1, Hyperdrive) work because they use lazy runtime resolution:

const binding = process.env.DB || globalThis.env?.DB

Non-CF deployments (postgres-js, neon-http, mysql2) don't have this.

I propose always use lazy resolution for non-CF drivers too. Zero config changes, Docker multi-client deployments would work:

function getDB() {
const url = process.env.DATABASE_URL || process.env.POSTGRES_URL
if (!url) throw new Error('DATABASE_URL required')
return drizzle({ connection: url, schema })
}

Also: only require DATABASE_URL at build time if applyMigrationsDuringBuild: true.

Should I open a PR @atinux ? Would close #777 as well.

Did i miss something?
Kenshi
—
Yesterday at 1:32 PM
We have it run checks and in case of changes migrations at the app launch. It might not be the cleanest solution but it works for our use case as of right now.
Vetro
—
Yesterday at 2:07 PM
Hey, I work with @kenshi . It would be great if migrations could be done on application deploy, not just on build.

Also I found, that probably whole hub's config is baked into nuxt's nitro.mjs on build... blob config what was in env file (api keys for S3) is also here
Atinux
—
Yesterday at 2:42 PM
sounds good!