🐛 Getting Started missing important information about wundergraph HOT 6 CLOSED

hi jens,
thank you for your reply. i think i can see it much clearer now what is happening "under the hood" :) i actually read the text "vs_hasura" that explained it quite good. maybe it is more concise to say: hasura at its core is a graphql to sql interpreter where wundergraph is a graphql to rest compiler and request/api router/gateway...

from wundergraph.

Thank you, we're working on open-sourcing the docs and will add your suggestions.

from wundergraph.

cd .wundergraph solves this problem with generate

next error will be on step wunderctl up --debug

error	watcher	{"watcher": "wundergraph config", "error": "lstat generated/wundergraph.config.json: no such file or directory"}
...
Could not load wundergraph.config.json. Did you forget to run `wunderctl generate` ?

indeed there is no such file :(

from wundergraph.

ok. i got it running. i had to modify wundergraph.config.ts i could successfully connect a sqlite db and define a query like: http://localhost:9991/app/main/operations/Posts?condition={%22title%22:{%22startsWith%22:%22Hello%22}}

i still have a hard time to "get it". i have a question: when running in production with the go server, is the sqlite process part of the go server? or is it running in some "shadow" node-js/prisma server?

from wundergraph.

There's a Go server (gateway) and a NodeJS server (hooks). If you're connecting to a database, the Go server spawns a prisma process and talks to it over HTTP. In theory, it would be possible to compile prisma to a shared object and load it from go directly. Then the gateway can talk to it in memory. However, this does not work on all systems, e.g. Windows doesn't work, but it could be enabled without many changes, at least on linux for production environments.

from wundergraph.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from wundergraph.