edgedb-examples VS edgedb-cli

Create a docs folder in the root of the project. Here we will place our Markdown documentation files. You can grab the files we use from the example project’s GitHub repo or add your own. (If you use your own, you may also want to adjust the system message we send to OpenAI later.)

EdgeDB employee here. Regarding tech stacks, we're seeing the most adoption in the JS/TypeScript ecosystem, especially Next.js and Remix users. That's followed by Python then Go. We've been prioritizing Deno and will be working in the near future to make our query builder Deno-compatible as well. You can see an (very simplistic) example project showing how to use EdgeDB in a Deno Fresh app: https://github.com/edgedb/edgedb-examples/tree/main/deno-fresh

We're still working out the kinks, but some form of this will definitely be possible.

You can already hack this by defining access policies and writing an EdgeQL proxy server that authenticates incoming requests, sets the appropriate global, and forwards the query to the database. There's a Python/Flask implementation of this pattern here[0].

We also have a JavaScript example app demonstrating access policies to simplify authorization logic using Next.js/getServerSideProps[1] and a user management platform you may have heard of called Clerk[2] :)

[0] https://github.com/edgedb/edgedb-examples/tree/main/flask-pr...

[1] https://github.com/edgedb/edgedb-examples/blob/main/nextjs-a...

[2] https://clerk.dev/

The initial schema creation is somewhat slow because the CLI is taking the slow route currently. Will be fixed soon in https://github.com/edgedb/edgedb-cli/issues/652