Running a Local Instance

Note

The goal of this page is to help you launcher dfuse for EOSIO as quickly as possible, on your local machine.

Initialize a new dfuse.yaml file in the current working directory:

dfuseeos init

Optionally copy over a boot sequence to have dfuse bootstraps your chain with accounts, system contracts to have a chain ready for development in matter of seconds:

wget -O bootseq.yaml https://raw.githubusercontent.com/dfuse-io/dfuse-eosio/develop/booter/examples/bootseq.dev.yaml

Note Check booter/examples for other boot sequence templates.

Boot your instance with:

dfuseeos start

A terminal prompt will list the graphical interfaces with their relevant links:

Dashboard: http://localhost:8081
Explorer & APIs:  http://localhost:8080
GraphiQL:         http://localhost:8080/graphiql

In this mode, two nodeos instances will now be running on your machine, a block producer node and a mindreader node, and the dfuse services should be ready in a matter of seconds.

Limitations

EOSIO networks can grow substantially. Running that on a laptop for a long period of time isn’t sustainable. Also, databases written with default values (for key value stores notably) can not be re-used for long-running deployments.

For a long-running instances, please refer to long-running deployments documentation.