This feature automates the setup of a development environment on Linux (Debian based) or MacOS.
Not thoroughly tested on MacOS.
The script will check to see if the development dependencies are installed on the development machine and proceed to install them if they can't be found.
Then, the script will make .config files for the needed number of nodes and run them for the user.
The script can be run with parameters that will tell the script how many nodes, how many workers per node, and how much cpu resources each node should be limited to.
If no parameters are provided, the script will default to 2 nodes with 3 workers each (min 4 cpu cores per node) and ask the user to confirm. If they don't the user is asked what they want to use.
Updated CONTRIBUTION.md and README.md docs to reflect the recent environment changes and added references to the run_testnet.sh script.
This feature automates the setup of a development environment on Linux (Debian based) or MacOS.
Not thoroughly tested on MacOS.
The script will check to see if the development dependencies are installed on the development machine and proceed to install them if they can't be found.
Then, the script will make .config files for the needed number of nodes and run them for the user.
The script can be run with parameters that will tell the script how many nodes, how many workers per node, and how much cpu resources each node should be limited to.
If no parameters are provided, the script will default to 2 nodes with 3 workers each (min 4 cpu cores per node) and ask the user to confirm. If they don't the user is asked what they want to use.
Updated CONTRIBUTION.md and README.md docs to reflect the recent environment changes and added references to the run_testnet.sh script.