config
Utilities for managing application configuration files. These commands provide comprehensive tools for viewing, modifying, and maintaining your Babylon node's configuration settings across different versions and deployments.
Overview
The config
command group provides utilities for managing Cosmos SDK application configuration files (app.toml) including reading, writing, migrating, and comparing configuration values.
babylond config [command] [flags]
Quick Reference
Command | Description | Use Case |
---|---|---|
diff | Show config differences from defaults | Configuration auditing |
get | Get a specific config value | Value retrieval |
home | Show the home directory path | Path verification |
migrate | Migrate config to specified version | Version upgrades |
set | Set a config value | Configuration updates |
view | View entire config file | Configuration inspection |
Global Flags
Flag | Type | Default | Description |
---|---|---|---|
--home | string | ~/.babylond | Directory for config and data |
--log_format | string | plain | The logging format (json |plain ) |
--log_level | string | info | The logging level (trace |debug |info |warn |error |fatal |panic |disabled or '*:<level>,<key>:<level>' ) |
--log_no_color | Disable colored logs | ||
--trace | Print out full stack trace on errors |
diff
Outputs all config values that are different from the app.toml defaults. Useful for configuration auditing and identifying customizations.
Usage
babylond config diff [target-version] <app-toml-path> [flags]
Arguments
Argument | Description |
---|---|
target-version | Target version to compare against (optional) |
app-toml-path | Path to the app.toml file to compare |
Examples
babylond config diff ~/.babylond/config/app.toml
babylond config diff v1.0.0 ~/.babylond/config/app.toml
get
Get an application config value. The config argument must be the name of the config file without the .toml extension when used with babylond.
Usage
babylond config get [config] [key] [flags]
Arguments
Argument | Description |
---|---|
config | Config file name (without .toml extension) or full path |
key | Configuration key to retrieve |
Examples
babylond config get app minimum-gas-prices
babylond config get app api.enable
babylond config get app grpc.enable
babylond config get app grpc.address
# Check telemetry settings
babylond config get app telemetry.enabled
# Check state sync settings
babylond config get app state-sync.snapshot-interval
# Check pruning configuration
babylond config get app pruning
home
Outputs the folder used as the binary home directory. The path can be changed by setting the $APPD_HOME
environment variable or using the --home
flag.
Usage
babylond config home [flags]
Examples
babylond config home
HOME_DIR=$(babylond config home)
echo "Babylon home: $HOME_DIR"
babylond config home --home /custom/babylon/path
migrate
Migrate the contents of the Cosmos SDK app configuration (app.toml) to the specified version. The output is written in-place unless --stdout
is provided.
Usage
babylond config migrate [target-version] <app-toml-path> [flags]
Flags
Flag | Type | Description |
---|---|---|
--skip-validate | Skip configuration validation (allows migrating unknown configurations) | |
--stdout | Print the updated config to stdout | |
--verbose | Log changes to stderr |
Arguments
Argument | Description |
---|---|
target-version | Version to migrate the configuration to |
app-toml-path | Path to the app.toml file to migrate |