Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Problem: Docs needed a more specific description of how to input the path to the private-key file

Browse Source 
Solution: Changed the wording a bit
This commit is contained in:
z-bowen 2018-08-23 16:39:49 +02:00
parent e5d3e74cdd
commit cce153e217
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/server/source/server-reference/bigchaindb-cli.md
View File

@ -117,8 +117,8 @@ If the command succeeds, it will create an election and return an `election_id`.
```bash
$ bigchaindb upsert-validator approve <election_id> --private-key PATH_TO_YOUR_PRIVATE_KEY
```
Here, `<election_id>` is the transaction id of the election the approval should be given for. `--private-key` should be
the path to wherever the private key for your validator node is stored, (*not* the private key itself).
Here, `<election_id>` is the transaction id of the election the approval should be given for. `--private-key` should be the path to Tendermint's private key which can be generally found at `/home/user/.tendermint/config/priv_validator.json`.
Example usage,
```bash
$ bigchaindb upsert-validator approve 04a067582cf03eba2b53b82e4adb5ece424474cbd4f7183780855a93ac5e3caa --private-key /home/user/.tendermint/config/priv_validator.json