Warning! This is intended for developers to construct debug builds. Other users are advised to use the docker files as outlined in the main readme.md

• Introduction
• One time machine configuration
• New debug session setup

0Chain setup for running directly on machines. This allows the for debugging running chains. The documentation is presented from the perspective of an Ubuntu machine but should apply equally to a Mac or alternative Linux OS.

As 0chains need at least three or four miners. When running outside docker containers only one miner and one sharder is permitted on each machine, each such 0chain needs to be run over at least three machines.

Each machine needs to be configured so that 0chain executables can be built, outlined in build_environment.md and the database 0Chain uses installed as in install_dbs.md

If you are using an IDE such as Goland, you will want to set up you debug environments as outline in debug_environment.md

Each time you start a new chain you will have to ensure all the various configuration files across the 0chian network's machines are correctly setup, as outlined in debug_environment.md

Each time you start a debug session you will want to do something similar to the following. If you don't mind a slightly dirty environment you might skip resetting the databases.

If you are running a miner use docker

sudo local/bin/docker.run.redis.sh

or if not using docker

sudo local/bin/reset.redis.sh

TODO: Add docker setup for cassandra

If you are running a sharder

sudo local/bin/reset.cassandra.sh

Wait for cqlsh to come up then

local/bin/init.cassandra.sh

Now clear and rebuild the runtime directories

local/bin/clean.sh
local/bin/init.setup.sh

You can enter your IDE run your 0chain apps; Remembering to start sharders first.