The most straight forward way of creating a new server configuration is using the command
vnode new which allows you to configure the most basic settings.
By default the node configuration file is stored at user level, which isolates this configuration from other users. In case you want this configuration to be available for all users, simply add the
The configuration wizard outputs a YAML file which can be loaded into Joey. It is also possible to create this file yourself, to see Configuration File Structure or an example on our github page. This file can be stored (and referred to) at any location at the machine, although it recommended to use either the Joey system or user folder. These folders are different per operating system.
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.
In the section above we used the
vnode command several times. All sub-commands can be found by simply running
vnode , which will display the following list:
Create a new configuration file
List all available configurations (both system/user)
List file locations of the node instance
Start a node configuration
Each node instance (configuration) can have multiple environments. If you do not want to specify any environment you should only specify the
application key. In the case you do want to use environments you can specify this in
environments which allows up to four environments:
prod . It should have the following structure:
application:api_key: api-key-from-serverserver_url: https://api.distributedlearning.aiport: 5000api_path: '/api'task_dir: tasksencryption:private_key: /path/to/private_key.pemdatabases:default:logging:level: DEBUG # Can be on of 'DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'file: node.log # Filename of logfileuse_console: True # Log output to the console?backup_count: 5 # Number of logs to keepmax_size: 1024 # Specified in kB (i.e. 1024 means a maximum file size of 1MB)format: "%(asctime)s - %(name)-14s - %(levelname)-8s - %(message)s"datefmt: "%H:%M:%S"