6452898b-4334-4a3f-b118-d8bfb71e8f8c

Hi! Did you try the "Shared Monorepos" guide?

Yes! I used it to deploy the backend and the frontend, but the database package needs a .env inside to run the migrations. I don't really know how to proceed on that inside Railway

And may I ask why don't you have a .env with the needed vars in that package? That's how turborepo works, all my packages have their own env file

I do have! But I need to add the envs inside the package on Railway too

Oh, now I got it.

Yes, that's the problem

Are you using dotenv?

hmm, nope

I am using a package called @t3-oss/env-nextjs

and did you set the runtimeEnv property in the env.mjs file?

I did! The problem is: I need to create a ".env" for the database package inside railway. In my local environment it works perfectly because inside the database package I have the .env file, but i need it inside railway as well for it to work and run the migrations

can you show me your drizzle.config.ts? you can hide any sensitive info there

Of course!

use process.env.DATABASE_URL

that's the issue

I did this to validate the env as well as soon as keys() is not being used anymore

cool! did it work?

Not yet!

Do I need to keep the .env inside /database package?

no!

but I see other issue

"no config path provided"

oh nvm it looks for the root one either way

yes!

This is local, right? could u try in a staging env on railway?

yes! it's in local environment

i don't see how it's going to help running on staging env on railway, could you elaborate on that?

I had a project (not a monorepo) that used dotenv to setup env vars, upon deploying on railway it would conflict and would not use the Railway injected env vars.

locally it would work fine

hmm, i dont think it's related to that tbh

but ill try

In the end I solved it by removing dotenv and upgrading to bun and using Bun.env.

I wonder if nextjs-env is doing something similar with your project