Re standalone docker

This page contains information about building and running a Re node in a standalone way.

Prerequisites​

Build and run​

1. Make sure you have the required Golang version​

go version

2. Clone Re repository and cd into it​

git clone https://github.com/jim380/Re.git
cd Re

3. Build a Re node image​

make build-docker-image

4. Run a Re node as a docker container​

make start-docker-container

A Re node is now running in the background. To see the app logs, run:

docker ps

And use the re-node container ID in the following command:

docker logs -f <re-node-contained-id>

To stop the node, run

make stop-docker-container

Usage​

Ports​

The Re node exposes several ports to be used by you and your applications:

  • 1317:1317 — the REST server;

  • 26657:26657 — the Tendermint RPC server;

  • 26656:26656 — the Tendermint P2P server;

  • 9090:8090 — the gRPC server.

Interaction with the node using red​

The Re node is available to be interacted with using red command. The following command will install red on your computer:

make install

This command builds the red executable using the latest version of the Re Protocol and installs the resulting binary in your GOBIN directory. Ensure that GOBIN is defined and included in the PATH environment variable. This ensures that the installed binary can be accessed globally on your system. If you encounter any issues during this process, troubleshoot them by verifying that your Golang-related environment variables are correctly set.

After the installation process is complete, the red executable is ready to be used:

red query bank total

Making transactions​

There are several accounts added at the genesis state that possess RE and are at your service. See the genesis init script to find out more details about it. The following command will list all the preallocated addresses:

docker exec <re-node-contained-id> red keys list --keyring-backend test --home data/test-1/

We suggest you add the accounts from the init script mentioned above to your local test keyring to make them useful directly from the command line. To do so, copy a mnemonic from the script and use it in a keypair recovery procedure:

red keys add <name> --recover --keyring-backend test
> Enter your bip39 mnemonic

After that, you'll be able to make transactions using any of the accounts and Queries

PreviousRe build from sourcesNextCore

Last updated