https://github.com/impay-money/bdjuno

Impay's WASM integrated bdjuno parser.
https://github.com/impay-money/bdjuno

Last synced: about 2 months ago
JSON representation

Impay's WASM integrated bdjuno parser.

• Host: GitHub
• URL: https://github.com/impay-money/bdjuno
• Owner: impay-money
• License: mit
• Created: 2023-06-16T00:04:20.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-09-13T17:27:24.000Z (about 1 year ago)
• Last Synced: 2024-06-12T06:39:05.146Z (3 months ago)
• Language: Go
• Size: 42.4 MB
• Stars: 1
• Watchers: 2
• Forks: 0
• Open Issues: 15
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# BDJuno

[![GitHub Workflow Status](https://img.shields.io/github/workflow/status/forbole/bdjuno/Tests)](https://github.com/forbole/bdjuno/actions?query=workflow%3ATests)

[![Go Report Card](https://goreportcard.com/badge/github.com/forbole/bdjuno)](https://goreportcard.com/report/github.com/forbole/bdjuno)

![Codecov branch](https://img.shields.io/codecov/c/github/forbole/bdjuno/cosmos/v0.40.x)

BDJuno (shorthand for BigDipper Juno) is the [Juno](https://github.com/forbole/juno) implementation

for [BigDipper](https://github.com/forbole/big-dipper).

It extends the custom Juno behavior by adding different handlers and custom operations to make it easier for BigDipper

showing the data inside the UI.

All the chains' data that are queried from the RPC and gRPC endpoints are stored inside

a [PostgreSQL](https://www.postgresql.org/) database on top of which [GraphQL](https://graphql.org/) APIs can then be

created using [Hasura](https://hasura.io/).

## Usage

To know how to setup and run BDJuno, please refer to

the [docs website](https://docs.bigdipper.live/cosmos-based/parser/overview/).

## Testing

If you want to test the code, you can do so by running

```shell

$ make test-unit

```

**Note**: Requires [Docker](https://docker.com).

This will:

1. Create a Docker container running a PostgreSQL database.

2. Run all the tests using that database as support.