parent
5ed1775681
commit
4ddfef6204
|
@ -39,3 +39,14 @@ Sentry Nodes should edit their config.toml:
|
||||||
# Comma separated list of peer IDs to keep private (will not be gossiped to other peers)
|
# Comma separated list of peer IDs to keep private (will not be gossiped to other peers)
|
||||||
private_peer_ids = "ipaddress of validator nodes"
|
private_peer_ids = "ipaddress of validator nodes"
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## Environment Variables
|
||||||
|
|
||||||
|
By default, uppercase environment variables with the following prefixes will replace lowercase command-line flags:
|
||||||
|
|
||||||
|
- `GA` (for Gaia flags)
|
||||||
|
- `TM` (for Tendermint flags)
|
||||||
|
- `BC` (for democli or basecli flags)
|
||||||
|
|
||||||
|
For example, the environment variable `GA_CHAIN_ID` will map to the command line flag `--chain-id`. Note that while explicit command-line flags will take precedence over environment variables, environment variables will take precedence over any of your configuration files. For this reason, it's imperative that you lock down your environment such that any critical parameters are defined as flags on the CLI or prevent modification of any environment variables.
|
||||||
|
|
Loading…
Reference in New Issue