dockerfolder with scripts for running a Hydra Indexer and Hydra Processor locally
.envwith all the necessary environment variables. It is pre-populated with the prompt answers but can be edited at any time.
package.jsonwith a few utility yarn scripts to be used later on.
schema.graphql, create the database schema and run all the necessary migrations.
generated/graphql-serverwith a ready-to-use Apollo GraphQL server powering the query node API.
manifest.ymlwhich defines which events and extrinsics are going to be processed by Hydra Processor. Two most important sections are
hydra-typegenis an auxiliary tool for generating typesafe event and extrinsic classes from the on-chain metadata. It is not strictly necessary to use it, but type safety significantly simplifies the development of the event and extrinsic handlers.
mappings/generated/typeswhere the newly created classes for the declared events and extrinsics will be generated.
mappingssection of the manifest file and reside in the
WS_PROVIDER_ENDPOINT_URIenvironment variable defines the node to connect. Additionally, one can map volumes as json files with runtime type definitions. The following environment variables
WS_PROVIDER_ENDPOINT_URI=wss://rpc.polkadot.iotogether with the database variables and run
hydraVersionmatches the one of
hydra-cliand declared in
.envto the local indexer
http://localhost:4000/graphqland you can find some transfers:
dockerfolder with Dockerfiles.
yarn db:bootstrapin the
builderimage. A similar setup strategy may be used for Kubernetes (with
builderas a starter container).