iorveth 68ecab08a3 Query node integration tests: move apollo-client dependency to the right place vor 4 Jahren
..
bootstrap 835b9dc8fd remove hydra related code vor 4 Jahren
mappings 32e21975d6 Revert .env, update content-dir-consts vor 4 Jahren
.dockerignore ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace vor 4 Jahren
.env 32e21975d6 Revert .env, update content-dir-consts vor 4 Jahren
.gitignore 76916dfdd6 query-node: do not check in generated code vor 4 Jahren
README.md ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace vor 4 Jahren
docker-compose.yml 649082bcea Query node integration tests: hardcode delay (temporary solution) vor 4 Jahren
indexer-tsconfig.json 9023b2b4ea Merge remote-tracking branch 'mokhtar/query-node/ignore-generated-code' into query-node-types vor 4 Jahren
package.json 6a53ff4ca5 query-node: symlink to typeorm vor 4 Jahren
run-tests.sh 1e76bbd32f query-node: extra check to for typeorm link, and checkin yarn.lock vor 4 Jahren
schema.graphql 86a14a5067 add happenedIn field to Language and VideoMediaEncoding entities vor 4 Jahren
tsconfig.json 94e8fb7ae8 Query node - fix @joystream/types issue vor 4 Jahren
typedefs.json ca0f390137 update typedefs from types vor 4 Jahren

README.md

query-node

The query-node project contains an input schema (schema.graphql) and mappings for the Joystream content-directory runtime module.

Code generation

We use Hydra-cli to generate a graphql server and a block indexer for joystream chain:

$ cd query-node
$ yarn build

Run mapping processor

Before running mappings make sure indexer(yarn indexer:start) and indexer-api-server (mappings get the chain data from this graphql server) are both running:

yarn processor:start

Query data

Once processor start to store event data you will be able to query this data from http://localhost:4002/graphql.

query {
  channels {
    title
  }
}