Hello, team! I’m very excited to join the community. I have a question for setting up the development environment. I followed the instruction here: https://github.com/calcom/cal.com#development: copied the

.env

files and ran

yarn dx

, but I got:

@calcom/web:dx:     '  error: Environment variable not found: DATABASE_URL.\n' +
@calcom/web:dx:     '  -->  schema.prisma:6\n' +
@calcom/web:dx:     '   | \n' +
@calcom/web:dx:     ' 5 |   provider = "postgresql"\n' +
@calcom/web:dx:     ' 6 |   url      = env("DATABASE_URL")\n' +
@calcom/web:dx:     '   | \n' +
@calcom/web:dx:     '\n' +

This error is gone if I add

DATABASE_URL

to

apps/web/.env

. Am I (or the docs) missing anything? 🤔

I needed to add db url myself to root env too

Just tried adding

DATABASE_URL

to root

.env

, doesn’t work for me. Same error

and in apps/web ? Sorry !

No worries, apps/web works, which is what I would expect. Should I raise a small PR to add it back in

apps/web/.env.example

? I wonder what is the reason behind putting it in

packages/prisma

🤔

@Thang Vu Thank you Thang 😃, lets ping @zomars which is leading the monorepo transition, I think we had good reason to have it in prisma package, but we need to make sure that .env is correctly passed from the package to other packages requiring it

My bad, it seems like the env is required in both

packages/prisma

and

apps/web

. Without it,

packages/prisma

would fail its own Prisma commands

Regardless we might need to either fix that or be more explicit about it in the docs/README/env files itself, thanks for reporting Thang

Happy to help, @Agusti 😄

The env variables is taken from the directory where the command is being called from

Btw I think we can explicitly allow some env vars in next.config if we want to so they don't need to be explicitly PUBLIC

Yeah, but we're trying to avoid that and also we like the public variables should be explicit