Node Configuration Reference
Configure the nodename, platform paths and Erlang VM parameters.
Node Identity
A distributed Bondy system consists of a number of Bondy router instances communicating with each other. Each such instance is called a node and must be given a name.
Name of the Bondy node.
The format of the nodename is a string name@host:
nameis the name given by the user, whilehostis the full host name.
The nodename is the node unique identifier within a cluster and thus each nodename must be unique.
DEPRECATED
Use environment variable BONDY_ERL_NODENAME instead
This is the Distributed Erlang magic cookie. Bondy doesn't actually use distributed Erlang for clustering, so this is not required for deploying a cluster.
However, if you want to connect to Bondy via an Erlang remote shell—e.g. by executing bondy remote_console on the host, VM or container running Bondy—we will need this option to be set.
Security
We recommend changing this value a secret value to prevent unauthorised users to gain access to Bondy's underlying Erlang VM.
DEPRECATED
Use environment variable BONDY_ERL_DISTRIBUTED_COOKIE instead
Paths
DEPRECATED
Use environment variable BONDY_DATA_DIR instead
DEPRECATED
Use environment variable BONDY_DATA_ETC instead
DEPRECATED
Use environment variable BONDY_DATA_LOG instead
DEPRECATED
Use environment variable BONDY_DATA_TMP instead
Erlang Virtual Machine
The following are advanced params and require knowledge of the Erlang VM. Read more at: http://erlang.org/doc/man/erl.html.
Sets the number of threads in async thread pool. If thread support is available, the default is 64.
The number of concurrent ports/sockets.
erlang.W