ignite / backend Goto Github PK

Setup the CI to automatically deploy a server that indexes of Ignite Chain:

• Chains from coordinators
• Chains from validator participation

In the Query Service we'll have proto definitions that describes the Mapper RPC.

We should enable grpc-web (through a Go gRPC handler) in the Query Service so we can support connections from a browser to the Mapper RPC.

We should setup a CI workflow that will do a TS client (code) generation from Mapper RPC proto files and publish to NPM as a package.

This workflow should run whenever we make new release in the repo.

• It should first check if the proto files in the Query Service changed (git diff the dir by using an action)
• If there is a change then trigger the process of generating a TS client and publishing it to the NPM registry with the same release version.

as another service. deprecate tendermint/backend afterwards.

publish the client of this service in an NPM package (one NPM package can be used to host all clients to different services), same as: #3

cc @fadeev

we probably need to proto unmarshal custom message types in TXs.

should/can we also store the TX responses?

unit tests, linters, publish docker images.

feel free to open multiple -small- PRs

Initialize a readme explaining the purpose of the project and the commands to run the server

depends on ignite/cli#2488