Building the Edgeware software

  1. First we log in to our server (preferably using software like Putty). For those who are new to Putty and SSH keys, here is a very good guide.
  2. Install the server itself and check for updates
  3. sudo apt-get upgradesudo apt-get update
  4. After making sure we are in the home directory using the command
  5. cd we want to clone the Edgeware node repository
  6. git clone https://github.com/hicommonwealth/edgeware-node.git
  7. After this we can want to make sure if everything went well by checking the content of the home directory using
  8. ls -a
  9. This explores the directory. A folder called “edgeware-node” should appear.
  10. Now we need to get into the edgeware-node folder
  11. cd edgeware-node
  12. From inside this directory, we want to run the automated script that’ll set up all the necessary prerequisites and then install the node.
  13. ./setup.sh
  14. This command will run for a longer time (in the range of hours). We usually see warnings similar to the one below while the setup script is running. These can be ignored.

    Running the node

  1. To run the node we first test it using
  2. ./target/release/edgeware --chain=edgeware --name
  3. Instead of type the name that you want to appear publicly in the testnet explorer.
  4. The node should start synchronizing blocks with other already running nodes. We can check if it is running by finding the name of our new node in the list on the Polkadot Edgeware testnet explorer

    Keeping the node online

  1. The node will shut down when we log out from the VM. We need to set it up so it will be running even when we close our Putty terminal. To do that, first we need to log out. Let’s do this using the command
  2. logout
  3. Now we log into our server again using Putty and get in the edgeware-node folder using
  4. cd edgeware-node
  5. Putting in the next command with our node name will ensure it stays online even after logging out.
  6. nohup ./target/release/edgeware --chain=edgeware --name
  7. Check if the node is running through the explorer.