docs: update docs on configuration and CLI#418
Conversation
| | `--config <path>` | Config file path. Defaults to `~/.config/piri/config.toml` | | ||
| | `--log-level <level>` | Logging level (debug, info, warn, error) | | ||
| | `--data-dir <path>` | Storage service data directory | | ||
| | `--temp-dir <path>` | Storage service temp directory | |
There was a problem hiding this comment.
We should remove this, it's basically unused.
There was a problem hiding this comment.
Agreed, will need to land as a separate change, iirc its still use by a blob store for writes.
| | Flag | Description | | ||
| |------|-------------| | ||
| | `--network <network>` | Network to join (`forge-prod` for mainnet, `warm-staging` for calibration) | | ||
| | `--data-dir <path>` | Directory for permanent Piri data (blobs, database) | |
There was a problem hiding this comment.
I assume this will become optional with postgres support?
There was a problem hiding this comment.
With just postgres? No, blobs still need a filesystem.
With postgres and s3, also no since the keystore (contains the users wallet for signing) is remaining filesystem-based. At present, we are opting to keep that on the filesystem, outlined in "Security Invariant" section here: #417
| ## Example | ||
|
|
||
| ```bash | ||
| piri status upgrade-check && piri update |
There was a problem hiding this comment.
How does this work...because piri update says it does not restart the service?
Do you want something more like this?
piri update && piri status upgrade-check && <restart-cmd>Where restart-cmd is something like sudo systemctl restart piri?
There was a problem hiding this comment.
Where restart-cmd is something like sudo systemctl restart piri?
Yea, more-or-less. The update command is primarily a convenience command outside of the auto-update flow which is still hidden and undocumented...
e76c62c to
b8bb044
Compare
8678013 to
d44f547
Compare
Will maintain this as #417 #416 and #409 land.