|
|
|
@ -73,7 +73,7 @@ The options below are all specified on the command-line.
|
|
|
|
|
|
|
|
|
|
* `-config-dir` - A directory of configuration files to load. Consul will
|
|
|
|
|
load all files in this directory with the suffix ".json". The load order
|
|
|
|
|
is alphabetical order, and the the same merge routine is used as with the `config-file`
|
|
|
|
|
is alphabetical, and the the same merge routine is used as with the `config-file`
|
|
|
|
|
option above. For more information on the format of the configuration files,
|
|
|
|
|
see the [Configuration Files](#configuration_files) section.
|
|
|
|
|
|
|
|
|
@ -85,12 +85,12 @@ The options below are all specified on the command-line.
|
|
|
|
|
shared folders) may not be suitable.
|
|
|
|
|
|
|
|
|
|
* `-dc` - This flag controls the data center in which the agent is running. If not provided,
|
|
|
|
|
it defaults to "dc1". Consul has first-class support for multiple data centers but
|
|
|
|
|
it defaults to "dc1". Consul has first-class support for multiple data centers, but
|
|
|
|
|
it relies on proper configuration. Nodes in the same data center should be on a single
|
|
|
|
|
LAN.
|
|
|
|
|
|
|
|
|
|
* `-encrypt` - Specifies the secret key to use for encryption of Consul
|
|
|
|
|
network traffic. This key must be 16-bytes that are Base64 encoded. The
|
|
|
|
|
network traffic. This key must be 16-bytes that are Base64-encoded. The
|
|
|
|
|
easiest way to create an encryption key is to use `consul keygen`. All
|
|
|
|
|
nodes within a cluster must share the same encryption key to communicate.
|
|
|
|
|
The provided key is automatically persisted to the data directory and loaded
|
|
|
|
|