Greetings all, I cloned the `calcom/cal.com` repo...
# docker
a
Greetings all, I cloned the
calcom/cal.com
repo, ran
yarn dx
and I'm able to use the self-hosted version except the enterprise features. I've already generated a license key from console.cal.com for a deployment and put that inside the
.env
file under
CALCOM_LICENSE_KEY
. Still, I keep saying the "This is an enterprise feature" dialogue under generating API keys for a user. Any help would be appreciated 🙂
p
@zomars can you investigate?
are you using docker @Ayaan Zaidi? if yes, potentially none of the .env are being picked up?
a
@Peer not using docker, just simple
yarn dx
. My
NEXTAUTH_SECRET
var gets picked up just fine in the same file
p
ok weird. @zomars any ideas why the key is not working?
c
I'll peek as well
CALCOM_LICENSE_KEY is missing from the docker side, will get that added
@zomars is this another build-time variable? I know we've talked about it before, I just need a reminder
z
It is not needed at build time. But if you're using Vercel you might need to redeploy. Yarn dx is meant for local development only
a
@zomars I understand, but I'd like to generate some keys locally first to explore the API. Is that possible or are those allowed to be generated only in production?
z
Also @Ayaan Zaidi which steps did you follow exactly?
a
@zomars the ones from the GitHub readme. Clone, yarn and dx. Copied the
.env.example
to
.env
and added the
openssl
secrets
Hey @Colin - Krumware, has the issue been identified? I tried a fresh setup and I'm still facing the problem.
Morning @Peer, could I please get an update on this issue?
p
can you book cal.com/zomars for a screenshare? I cant reproduce your issue on my end 😞
a
Okay sounds good!