After having a server up and running, we need to create and configure the nodes.
Similar to the server, nodes are created from a configuration file. This file can be generated through the command
vnode newor manually from a YAML file manually, as explained in this section.
If you're running any node in a collaboration that requires end-to-end encryption, you'll need to setup a private key for your organisation. This can be done through the command
Running this command without any arguments, will perform the following steps:
prompt for a node configuration to use
prompt for a username/password
retrieve the name of the organisation from the server
create a public/private key pair
update the node's configuration to point to the (new) private key
upload the public key to the server
If a key already exists (in step 4), the existing key is reused. This way, it's easy to configure multiple nodes to use the same key. All nodes within an organisation should use the same private key! Otherwise at least one of the nodes will not be able to process its tasks!
Once a configuration is created you can start this instance by using
vnode start and select the configuration you wish to start. Or in the case you already know the name of the configuration you can use
vnode start --name [config_name] . It is also possible to use a configuration file that is in a non-default location by using
vnode start --config /path/to/config . All other options will be overwritten when using this option.
The easiest way to read the logs from a node is using
vnode attach and select the node from which you want to read the logs from.
As a reference, these are the sub-commands available to manage the node(s). These commands can also be found by simply calling
Create a new configuration file
List all available configurations (both system/user)
List file locations of the node instance
Start a node configuration
Connect the console to the node's
Creates and uploads a new public key