Mokhtar Naamani ada62e5d88 hydra-cli v0.0.23 4 anos atrás
..
bootstrap 835b9dc8fd remove hydra related code 4 anos atrás
mappings 6053375748 query-node: name consistency - use camelCase 4 anos atrás
scripts 99aca3000b add script to get content-dir classes(id,name) from the chain 4 anos atrás
.env fa2ceae725 query-node: fix network-name 4 anos atrás
.gitignore 76916dfdd6 query-node: do not check in generated code 4 anos atrás
README.md ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace 4 anos atrás
build.sh f662b6fdda query-node: clean build 4 anos atrás
indexer-tsconfig.json bdb01a7d87 add esModuleInterop flag to indexer-tsconfig.json 4 anos atrás
package.json ada62e5d88 hydra-cli v0.0.23 4 anos atrás
run-tests.sh 547b64d070 start scripts forgot to bring up graphql-server 4 anos atrás
schema.graphql 1f20b19c9a query-node: rename fts query name for Video, Channel to `search` 4 anos atrás
tsconfig.json 94e8fb7ae8 Query node - fix @joystream/types issue 4 anos atrás
typedefs.json ca0f390137 update typedefs from types 4 anos atrás

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