Moving A Node Pilot Instance
Node Pilot is designed to be as portable as possible. This is important because hardware requirements may change frequently as chains update their node clients.
All settings and configurations are transferred over when following this guide.
NOTE: For these instructions, (A) represents the old instance, and (B) represents the new instance.
PORT FORWARDING: If you are running either instance of Node Pilot behind a home router or firewall, you will need to set up port forwarding for port 22. Transferring a Node Pilot config will require port 22 accessible by both (A) and (B).
CUSTOM CHAIN DIRECTORIES: If you opted to use custom "Chains Directory" when creating a node, then when migrating you will need to either: 1. Have the same paths availble in the new instance 2. Change the Chain Data location for the effected nodes in
If Node Pilot was run on machine(B), then the
/.node-pilotfolder needs to be deleted. DO NOT RUN THIS COMMAND ON MACHINE(A)! Delete via CLI:
rm -r ~/.node-pilot
3. Create a new
.node-pilotfolder on machine(B) in the home directory
Click "BACKUP" to download a backup ZIP of your config folder. If your backup includes Pocket nodes, the file could be many gigabytes which will take a few minutes before the download begins.
DO NOT NAVIGATE AWAY FROM THIS PAGE UNTIL THE FILE IS SAVED.
scp -r '/home/<USER(1)>/.node-pilot/config' <USER(2)>@<DOMAIN NAME>:/home/<USER(2)>/.node-pilot/
./np start -d