Add safe configuration commands
This commit is contained in:
parent
c20cc47914
commit
443602a30b
7 changed files with 432 additions and 3 deletions
|
|
@ -67,6 +67,27 @@ Set `RUST_LOG=geth_node=debug` when more daemon diagnostics are useful. Use
|
|||
`geth --home <dir> ...` to operate an isolated home without exporting an
|
||||
environment variable.
|
||||
|
||||
## Inspect And Change Configuration
|
||||
|
||||
User story: as an operator, I want to find and validate the exact configuration
|
||||
used by one geth home without guessing an OS-specific path or hand-editing
|
||||
common boolean and interval settings.
|
||||
|
||||
```sh
|
||||
geth config path
|
||||
geth config show
|
||||
geth config set sync.live_sync_interval_ms 10000
|
||||
geth config validate
|
||||
geth daemon stop
|
||||
geth daemon start
|
||||
```
|
||||
|
||||
`config show` reports built-in defaults when the file has not been created yet.
|
||||
`config set` preserves unrelated TOML and comments and refuses to replace the
|
||||
file if the complete prospective configuration is invalid. Success means
|
||||
`config validate` identifies the selected path as valid. Configuration is
|
||||
loaded at daemon startup, so restart the user service after changes.
|
||||
|
||||
## Establish An Owner Trust Root
|
||||
|
||||
User story: as the mesh owner, I want my first node rooted in an existing SSH
|
||||
|
|
|
|||
Loading…
Reference in a new issue