Home Verkennen Help
Inloggen
Operations
/
joystream
3
0
Vork 0
Bestanden Issues 0 Pull-aanvragen 0 Wiki
Boom: 9ba3b7acdd
Aftakkingen Labels
joystream
/
query-node
Mokhtar Naamani 8361d337e6 query-node: esInterop 4 jaren geleden
..
bootstrap 835b9dc8fd remove hydra related code 4 jaren geleden
mappings 32e21975d6 Revert .env, update content-dir-consts 4 jaren geleden
.env 32e21975d6 Revert .env, update content-dir-consts 4 jaren geleden
.gitignore 76916dfdd6 query-node: do not check in generated code 4 jaren geleden
README.md ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace 4 jaren geleden
build.sh f662b6fdda query-node: clean build 4 jaren geleden
indexer-tsconfig.json 8361d337e6 query-node: esInterop 4 jaren geleden
package.json 1cc6100faf docker: consolidate docker-compose files 4 jaren geleden
run-tests.sh 1cc6100faf docker: consolidate docker-compose files 4 jaren geleden
schema.graphql 86a14a5067 add happenedIn field to Language and VideoMediaEncoding entities 4 jaren geleden
tsconfig.json 94e8fb7ae8 Query node - fix @joystream/types issue 4 jaren geleden
typedefs.json ca0f390137 update typedefs from types 4 jaren geleden

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