Blockpool Commander
Following up on last weeks post, here are instructions as to how to actually set up a node and become a Delegate.
Blockpool Commander allows novice delegates to have an easier time installing and managing their BPL Nodes on your already existing VPS and VMs. In this article I will go over the steps to install BPL Node using Blockpool Commander. I would like to thank the ARK team and tharude for providing the code which we ported over to work with our Masterchain.
This guide will be fairly long due to the screenshots. If you are a more advanced user I have provided the commands in order at the bottom of this walkthrough.
Reminder: Do not run BPL Commander as root! You can cause install problems and introduce security issues.
git clone https://github.com/blockpool-io/BPL-Commander.git
cd BPL-Commander
chmod 777 BPLcommander.sh
./BPLcommander.sh
BPL commander will ask for your sudo password. If you are hosting on a service that uses a private key, no action will be needed.
Press enter
Wait for the process to complete
sudo reboot
Log back into your system
cd BPL-Commander
./BPLcommander.sh
BPL Commander will check for system updates. If no more updates are found it will skip to the menu screen
Press 1 then enter
BPL Commander will then download and install BPL-Node
Once that is complete the script will ask for your delegates secret press enter
Copy/Paste in your delegates secret passphrase and press enter
You will then be asked if you wish to apply this to your Node configuration. Press Y then enter
The script will update all necessary information in the configuration file and check if the BPL Node process is running. If the process is not running it will start it. Press Enter
Press 0 and enter to exit the script.
To check that the node is syncing the chain do the following
cd .forever
dir
Your log file will change each time you reboot the node. This time the file for me was called BRdU.log
tail -f BRdU.log
You will see the following scrolling up the screen. Congratulations! Your node is currently syncing. This can take some time so be patient. Once the block containing your delegate registration is passed your delegate will become enabled automatically.
Sometimes the node does not always switch over. This could be because of various different reasons. It is important to monitor your node while it’s syncing to ensure the switch happens as planned. If your node does not switch over from a relay node to delegate reopen BPL Commander and when you see the command prompt press R. This will reboot the node software.
Condensed Version:
git clone https://github.com/blockpool-io/BPL-Commander.git
cd BPL-Commander
chmod 777 BPLcommander.sh
./BPLcommander.sh
BPL commander will ask for your sudo password. If you are hosting on a service that uses a private key, no action will be needed.Press enterWait for the process to complete
sudo reboot
Log back into your systemcd BPL-Commander
./BPLcommander.shBPL Commander will check for system updates. If no more updates are found it will skip to the menu screen
Press 1 then enter
BPL Commander will then download and install BPL-Node
Once that is complete the script will ask for your delegates secret press enter
Copy/Paste in your delegates secret passphrase and press enter
You will then be asked if you wish to apply this to your Node configuration. Press Y then enter
The script will update all necessary information in the configuration file and check if the BPL Node process is running. If the process is not running it will start it. Press Enter
Press 0 and enter to exit the script.To check that the node is syncing the chain do the followingcd ..
cd .forever
Dir
Your log file will change each time you reboot the node. This time the file for me was called BRdU.log
tail -f BRdU.log
You will see the following scrolling up the screen. Congratulations! Your node is currently syncing. This can take some time so be patient. Once the block containing your delegate registration is passed your delegate will become enabled automatically.
Sometimes the node does not always switch over. This could be because of various different reasons. It is important to monitor your node while it’s syncing to ensure the switch happens as planned.
Originally published at docs.google.com.
