Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Getting Started missing important information #34

Closed
hinogi opened this issue Jun 8, 2022 · 6 comments
Closed

馃悰 Getting Started missing important information #34

hinogi opened this issue Jun 8, 2022 · 6 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation meta: stale

Comments

@hinogi
Copy link

hinogi commented Jun 8, 2022

Bug description

https://wundergraph.com/docs/guides/your_first_wundergraph_application/overview out of date, missing information like where to execute wunderctl

How to reproduce

  1. npm i -g @wundergraph/wunderctl@latest
  2. mkdir test-wundergraph && cd test-wundergraph
  3. wunderctl init
  4. npm install
  5. wunderctl add wundergraph/weather wundergraph/countries
  6. Open the file wundergraph.config.ts to adjust the configuration.
  7. wunderctl generate <-- Error

Expected behavior

Hint the reader to change the folder to .wundergraph or make the wunderctl search in .wundergraph

WunderGraph information

https://wundergraph.com/docs/guides/your_first_wundergraph_application/overview

Environment & setup

  • OS: OS: Windows 10 10.0.19044
  • Node.js version: 16.13.1

WunderCtl Version

Version: 0.90.32
Commit: 386a3d4b66204411dc89da6919aad0bebe524657
Date: 2022-06-06T12:22:22Z
BuiltBy: ci
@hinogi hinogi added the bug Something isn't working label Jun 8, 2022
@hinogi hinogi changed the title 馃悰 馃悰 Getting Started missing important information Jun 8, 2022
@jensneuse jensneuse added the documentation Improvements or additions to documentation label Jun 8, 2022
@jensneuse
Copy link
Member

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

@cwmoss
Copy link

cwmoss commented Jul 4, 2022

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 :(

@cwmoss
Copy link

cwmoss commented Jul 4, 2022

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?

@jensneuse
Copy link
Member

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.

@cwmoss
Copy link

cwmoss commented Jul 4, 2022

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...

@stale
Copy link

stale bot commented Sep 2, 2022

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.

@stale stale bot added the meta: stale label Sep 2, 2022
@stale stale bot closed this as completed Sep 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation meta: stale
Projects
None yet
Development

No branches or pull requests

3 participants