-
Notifications
You must be signed in to change notification settings - Fork 23
Migration guide (v1 to v2)
Tobiasz Cudnik edited this page Oct 18, 2019
·
8 revisions
This tutorial shows step-by-step instructions on how to migrate your old v1 RISE Node to the new v2 RISE network.
- Community agrees on a specific migration block (block on which everyone will switch their nodes)
- Everyone logs into their terminal and issues 2 commands - one to get the RISE CLI tool and one to start watching the block changes
- Once the migration block has been reached, RISE CLI will automatically stop, migrate and start the new version
- Migration is scheduled for
2019-10-18T14:00:18.194Z(Friday) at block2432687
- Log into your server and go to the RISE v1 directory
- Install Node.js v10
wget --quiet -O - https://deb.nodesource.com/setup_10.x | sudo bash; sudo apt install nodejs - Download RISE CLI
wget --quiet -O rise https://github.com/RiseVision/rise-node/releases/latest/download/rise; chmod +x rise - Run
screento keep the session active after you disconnect
sudo apt install screenif not installed - Run
./rise download - Run
sudo ./rise node install-deps - Run
./rise migrate - Wait till
2019-09-10T13:43:04.644Zfor the migration to happen - You can go back to the active session by running
screen -x
Starting a migrated RISE node is very similar to starting a regular v2 node, with the difference of --v1 param, which will automatically use the DB shipped with the previous version.
./rise node start --v1
./rise node status --v1
To find out more about RISE CLI, run ./rise.