Inicio Explorar Axuda
Iniciar sesión
Operations
/
joystream
3
0
Fork 0
Ficheiros Incidencias 0 Pull Requests 0 Wiki
Árbore: 4666ac7f8c
Ramas Etiquetas
joystream
/
query-node
Mokhtar Naamani 1e76bbd32f query-node: extra check to for typeorm link, and checkin yarn.lock %!s(int64=4) %!d(string=hai) anos
..
bootstrap 835b9dc8fd remove hydra related code %!s(int64=4) %!d(string=hai) anos
mappings 9b91908678 query-node: fix "happenedIn" property not defined VideoMediaEncoding graphql schema %!s(int64=4) %!d(string=hai) anos
.dockerignore ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace %!s(int64=4) %!d(string=hai) anos
.env e81df555c6 WIP - refactoring query_node %!s(int64=4) %!d(string=hai) anos
.gitignore 76916dfdd6 query-node: do not check in generated code %!s(int64=4) %!d(string=hai) anos
README.md ea241cf9f7 query-node: fix build scripts and remove generated code from yarn workspace %!s(int64=4) %!d(string=hai) anos
docker-compose.yml c95bc9ff31 query-node: test runner fix passing WS_PROVIDER_ENDPOINT_URI env variable %!s(int64=4) %!d(string=hai) anos
indexer-tsconfig.json 76916dfdd6 query-node: do not check in generated code %!s(int64=4) %!d(string=hai) anos
package.json 6a53ff4ca5 query-node: symlink to typeorm %!s(int64=4) %!d(string=hai) anos
run-tests.sh 1e76bbd32f query-node: extra check to for typeorm link, and checkin yarn.lock %!s(int64=4) %!d(string=hai) anos
schema.graphql 86a14a5067 add happenedIn field to Language and VideoMediaEncoding entities %!s(int64=4) %!d(string=hai) anos
tsconfig.json dff8a36993 query-node: update tsconfig %!s(int64=4) %!d(string=hai) anos
typedefs.json ca0f390137 update typedefs from types %!s(int64=4) %!d(string=hai) anos

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