metmirr 391ecbb7aa query-node: remove unused scripts před 4 roky
..
bootstrap 835b9dc8fd remove hydra related code před 4 roky
mappings 5ca2669ba8 query-node: remove babylon mappings před 4 roky
.gitignore 76916dfdd6 query-node: do not check in generated code před 4 roky
README.md fe235ebd3f query-node: configure with two separate databases před 4 roky
build.sh 807b498ec3 query-node: add hydra-processor and hydra-typegen to dependencies před 4 roky
manifest.yml d372d959b3 query-node: update package.json, manifest.yml před 4 roky
package.json a0ff9f4d92 query-node: bump hydra-cli version před 4 roky
run-tests.sh f3aa09d131 query-node: remove indexer from deps and clean up před 4 roky
schema.graphql dd32f719ba Merge remote-tracking branch 'upstream/babylon' into qnode-license-attribution před 4 roky
typegen.yml a54ef1334e query-node: add manifest.yml and typegen.yml před 4 roky

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

Starting services

To start services defined in the project docker-compose.yml, you should run docker-compose from the project root folder to use the correct .env file

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 {
    handle
  }
}