Releases: renproject/darknode-cli
Releases · renproject/darknode-cli
3.0.9
v3.0.8
v3.0.7
v3.0.6
v3.0.5
Minor fix and improvement :
- Show messages when starting executing the script.
- Update config format to the latest version in darknode.
- Remove
--config
flag form theupdate
command to avoid conflicts in the config file. - Show messages to tell if nodes have successfully been started/stopped/restarted.
- Minor tweak with the darknode installation script.
- Fix incorrect bootstrap addresses on testnet and devnet.
3.0.4
3.0.3
3.0.2
3.0.1
Changelog:
- Build binary for
arm
architecture and include it in the release. - Update bindings for darknode registry contract to the latest version.
- Not showing any error when failed to open registering url in a browser.
- Update prompt message to show the correct command when a new release is detected.
3.0.0 Chaosnet release
New CLI for Chaosnet darknodes deployment.
Since the config format for darknode is changed and we move from terraform 0.11.x to 0.12.x. New cli will not be backwards compatible with old darknodes. Users need to deregister and destroy old nodes first before updating to this version.
Changelog:
- Windows support with WSL
- Use updated
terraform
versionv0.12.12
- Release check before running any commands, it will warn users if they are using an old version.
- Support
start/stop/restart
commands to start/stop/restart the service on darknode. - Add
exec
command which allow users to run script/file on remote instance. - Add
register
command which shows the link to register a particular node and try opening it using the default browser. - Show provider information when running
darknode list
resize
command will not increase the disk size for digital ocean. (This allows users to downgrade their droplets after upgrading the plan)- Detail monitoring is enabled for all providers.
- Code has been refactored to be self-contained