-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloud databases #30
Comments
Hello there :) It sure is, you can take advantage of env variables to do so. From EdgeDB Cloud, you should be provided with a DSN to use, you can use that in development, or use a local instance in develpment and use that Cloud DSN in production. |
Hi! |
EdgeDB Cloud doesn't supply DSN information. Instead they give you a secret key and expect you to use the CLI. I've been trying to debug why this doesn't work properly in Vercel and from what I can tell the CLI isn't being installed in the environment in Vercel so even though I'm providing the EDGEDB_INSTANCE and EDGEDB_SECRET_KEY env vars it still doesn't work. Searching the code, the |
Yes, I tried yesterday to use the EdgeDB created in Vercel and connect the application using the provided credentials, but no success so far. |
From what I can see from the code for this repo, it expects the edgedb cli to be available, and if it is it tries to make use of that. What I think it needs to do after that is check for the environment variables EDGEDB_INSTANCE and EDGEDB_SECRET_KEY and attempt to connect with the cloud that way, otherwise it should continue to fallback to the DSN. The EdgeDB docs have Vercel working out of the box because the official EdgeDB JavaScript SDK looks for those env vars when it makes the connection. This just needs to do the same. |
Greetings!
Is it possible to make this module work with EdgeDB cloud? If so, can you explain how exactly?
Thank you!
The text was updated successfully, but these errors were encountered: