Skip to content

Latest commit

 

History

History
58 lines (41 loc) · 2.23 KB

README.md

File metadata and controls

58 lines (41 loc) · 2.23 KB
Raw

Development image for local deployment

This folder contains a Dockerfile for building a multi-component image that is well suited for spinning up a network using docker-compose for local development.

Usage

Two parameterized docker-compose files are available:

  • bakers.yaml: Run a network of bakers with collectors and a collector-backend. This is useful for e.g. testing the network dashboard. A middleware instance needs to be started separately.
  • bakers+wallet-proxy.yaml: Same as the above but also with a wallet-proxy instance running. A postgres instance is started as well and the nodes configured to ingest data. At the time of this writing, this setup seems outdated and broken and will be fixed ASAP.

It seems like there was an option that included a Middleware instance in the past. Including this will be attempted once the Wallet Proxy setup has been fixed.

Accounts

The images come with accounts with private keys for the accounts that are defined in genesis. This includes baker accounts. These keys are located in /genesis-data/genesis-$NUM_BAKERS-bakers/ directories. The baker accounts are under the bakers subdirectory, and any additional accounts are under the accounts subdirectory. They can be copied out either via docker cp when a container is running, or via docker run and mapping /genesis-data to a host directory.

Example

To boot a cluster of 5 nodes (no wallet-proxy), use the command

NUM_BAKERS=5 DESIRED_PEERS=4 docker-compose -f bakers.yaml up --scale baker=5 --force-recreate

Update the used docker image using

docker-compose -f bakers.yaml pull

...

Build

See dev-master.Jenkinsfile.

OLD

Information from the old README that might still be relevant:

Remember to clean out PostgreSQL data between runs using

$ NUM_BAKERS=5 DESIRED_PEERS=4 docker-compose -f develop.wallet-dev.yml down

Delay baker startup if PostgreSQL starts too slowly

If PostgreSQL starts too slowly the baker enabled for logging to it can be delayed by using the variable DB_SLEEP (the wallet-proxy has a default value of 30 set to delay start until PostgreSQL is up).