- Nxt Kit is an easy way to deploy/update Nxt on any number of your VPS or Dedicated Servers.
- !!! For the most of the people it is more convenient not to manage nodes by themselves.
- Supports almost any Linux distribution.
- Hallmarks nodes, changes config to make node public.
- Detects malfunctioning and automatically restarts client.
- Caches valid chain.
- Supports blockchain snapshots from Jelurida.
To deploy new version of Nxt, download it via
safe-nxt-download.sh, check file signature and execute playbook.
cd ~/nxt-kit/distrib ./safe-nxt-download.sh 1.1.4 # replace with the latest version. CHECK FOR OK ansible-playbook -f 10 -v ~/nxt-kit/playbooks/deploy.yml
You can also save the outbound traffic of the control machine by downloading a snapshot from Jelurida before running the playbook.
ansible nxts -m get_url -a "url=https://www.jelurida.com/NXT-nxt_db.zip dest=~/nxt-kit-deployed/distrib/chain-original-conf.zip force=yes" -f 10 -v
On managed VPS nodes
- Satisfy these requirements. For the latest Ubuntu/Debian/RedHat it would work out of the box.
- Configure SSH access using key authentication without password.
- If you are not paranoid
- add user to sudo with NOPASSWD for all commands.
- If you are paranoid
On control machine
- Install ansible and openssh-client.
- Add your servers to inventory group
exec ssh-agent bashto the end of
- SSH and exit to each of your managed node (to cache their public keys).
ssh-add ~/.ssh/PRIVATE-KEY-FOR-REMOTE-SERVER > /dev/null 2>&1to the end of the
~/.bashrcfor each private key for remote server.
- Clone this repo to
git clone https://github.com/nxt-ext/nxt-kit.git ~/nxt-kit.
- Put a valid zipped
~/nxt-kit/distrib/chain-original-conf.zip(optional). The archive from Jelurida is OK.
- If you was paranoid on managed nodes installation
- Remove dependency install block from
- There is a thread on NXT Forum for this tool. Feel free to discuss it there.
- Also you can PM me (EmoneyRu) on BCT or NXT Forum.