|
%!s(int64=4) %!d(string=hai) anos | |
---|---|---|
.. | ||
bootstrap | %!s(int64=4) %!d(string=hai) anos | |
mappings | %!s(int64=4) %!d(string=hai) anos | |
scripts | %!s(int64=4) %!d(string=hai) anos | |
.gitignore | %!s(int64=4) %!d(string=hai) anos | |
README.md | %!s(int64=4) %!d(string=hai) anos | |
build.sh | %!s(int64=4) %!d(string=hai) anos | |
db-migrate.sh | %!s(int64=4) %!d(string=hai) anos | |
indexer-tsconfig.json | %!s(int64=4) %!d(string=hai) anos | |
package.json | %!s(int64=4) %!d(string=hai) anos | |
processor-start.sh | %!s(int64=4) %!d(string=hai) anos | |
run-tests.sh | %!s(int64=4) %!d(string=hai) anos | |
schema.graphql | %!s(int64=4) %!d(string=hai) anos | |
tsconfig.json | %!s(int64=4) %!d(string=hai) anos |
The query-node project contains an input schema (schema.graphql) and mappings for the Joystream content-directory
runtime module.
We use Hydra-cli to generate a graphql server and a block indexer for joystream chain:
$ cd query-node
$ yarn build
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
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
Once processor start to store event data you will be able to query this data from http://localhost:4002/graphql
.
query {
channels {
handle
}
}