npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@metmirr/hydra-cli

v0.1.5-4

Published

CLI tool for building a Hydra query node

Downloads

3

Readme

Hydra CLI

A cli tool for running a Hydra query node

USAGE

$ hydra-cli [COMMAND]

COMMANDS

scaffold  Generate a starter project with a sample schema file and mappings
codegen   Generate a ready to run graphql server and block indexer
preview   Preview the output schema served by the GraphQL server

Architecture one-liner

A Hydra query node ingests substrate events in a multi-step pipeline which looks as follows:

Substrate Chain => Hydra Indexer => Indexer GraphQL gateway => Hydra Processor => Database => Query Node GraphQL endnpoint 

For popular chains the processor may connect to a publicly available Indexer endpoint (such as https://kusama-indexer.joystream.app/graphql for Kusama), otherwise a self-hosted indexer should be run.

Using Hydra CLI

Using npx:

$ alias hydra-cli='npx @dzlzv/hydra-cli'

or install via npm:

npm install -g @dzlzv/hydra-cli

and then

$ hydra-cli [COMMAND]

Getting Started

Run

$ hydra-cli scaffold

and answer the prompts. The scaffolder will generate the following files:

├── .env
├── docker-compose.yml
├── docker
├── mappings
├── package.json
└── schema.graphql

The scaffolder auto-generates sample mappings and an input schema file as a quick starter. The provided example simply tracks all the transfers in the chain and is not that interesting on its own.

Make sure a PostgresDB is running in the background. You may start it with docker:

docker-compose up -d db

Then run all the nessary migrations and codegen in a single run:

yarn bootstrap

Now you can start Hydra processor running the mappings in ./mappings against the indexer as configure in .env:

yarn processor:start

To run a GraphQL query node server run in a separate window:

yarn server:start:dev

A GraphQL playground will open up at localhost:4000. Try to query some Kusama transfers:

query {
  transfers(limit: 5, where: { value_gt: 1000000000000 }) {
    block
    value
    from
    to
  }
}

The schema and the queries can be inspected on the Schema and Docs tabs on the right.

For an in-depth guide on how to create complex schemas and supported features like full-text search, interfaces, union and algebraic types and more, check the Docs and also visit Hydra Webpage for a one-pager.

Dockerized quickstart

The easiest way to get the whole Hydra stack working inside a Docker container is to build a hydra-kit Docker image. The provided docker-compose.yml comes with a node-template image for a Substate chain and a Hydra indexer run against it.

First, build hydra-kit:

$ yarn docker:build

Let's start the db and run the migrations. hydra-kit will connect to the network running the database container created by docker-compose.

$ yarn docker:db:up
$ yarn db:prepare
$ yarn docker:db:migrate

Now everything is ready to run the whole stack locally:

$ yarn docker:up

After some warm-up time, the query node will be available at localhost:4000 and the indexer gateway playground at localhost:4001

Setting up the indexer

To run a self-hosted indexer, we need to spin up a local indexer together with a GraphQL gateway. The setup requires a redis and a db instance and thus is more convenient to run with a docker-compose file:

$ docker-compose up -d redis
$ docker-compose up -d indexer
$ docker-compose up -d indexer-api-gateway

If everything set up correctly, it should be possible to inspect the Indexer gateway at http://localhost:4001/graphql

Running the processor

Dockerized

When the indexer gateway is available (either locally or hosted elsewhere), the processor can be run againt it:

$ docker-compose up -d processor

For running against a hosted indexer gateway, simply change INDEXER_ENDPOINT_URL variable. For example, setting it to https://indexer-kusama.joystream.app/graphql will run the processor against events and extrinsincs in Kusama chain.

Running locally

For running the processor locally, run yarn processor:start

Running the query node endpoint

Finally, run the query node endpoint:

$ docker-compose up -d graphql-server

The query node is run at port 8080 by default.

To run it locally, inspect the settings in .env and run

$ yarn configure:dev
$ yarn server:start:dev