vdash is a terminal based dashboard for monitoring Safe Node (Vaults) on Windows, MacOS and Linux.
Now with live updating timelines for one or more vaults.
Left/Right arrow: cycle between nodes (vaults)
’i’ or ‘o’: zoom timeline in or out (’+’ or ‘-’ also work)
Update: vdash v0.3.0
Install from crates.io
See the README for more, but assuming you have Rust installed:
cargo install vdash vdash --help
If you are on Windows you need to clone the repo and build manually, as described in step 2c.
vdash can only be used with a baby-fleming local test network at this point, but will be updated for the new test networks when they emerge.
Use with a local test network
safe vault killall rm -f ~/.safe/vault/baby-fleming-vaults/*/safe_vault.log RUST_LOG=debug,quinn=error safe vault run-baby-fleming -t
- you need to make sure no existing vaults are still running, and deleting existing logfiles prevents you picking up statistics from previous activity.
- setting RUST_LOG ensures the logfiles contain the data which
vdashneeds, and excludes some that gets in the way.
For more info see the README which walks you through everything.
vdash you’ll see the vault logfiles growing (like using
tail -f) and can scroll up and down using the arrow keys. The display only shows one vault at a time, but if you passed multiple logfiles to
vdash you can cycle through them using TAB or the left/right arrow keys.
You’ll see the vault ages move fairly rapidly from Infant to Elder, and if you store some files with the Safe CLI (e.g.
safe files put -r <directory>) eventually the PUTs will show up too. Same for gets using
safe cat and so on.
Let me know if you have a go and how you get on.
PS There’s was a bug where after some time
vdash stops getting the updates to tell it the vault files have changed. I have attempted to fix this but am not sure it has solved the problem, so please let me know if it happens to you. You can just restart
vdash if this happens.