mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
Revised docs based on tips from user (#2611)
This commit is contained in:
parent
f0df5bd2e0
commit
d9725d483b
@ -81,7 +81,7 @@ from all the Members, and should combine them in the file
|
|||||||
"validators":[
|
"validators":[
|
||||||
{
|
{
|
||||||
"pub_key":{
|
"pub_key":{
|
||||||
"type":"AC26791624DE60",
|
"type":"tendermint/PubKeyEd25519",
|
||||||
"value":"<Member 1 public key>"
|
"value":"<Member 1 public key>"
|
||||||
},
|
},
|
||||||
"power":10,
|
"power":10,
|
||||||
@ -89,7 +89,7 @@ from all the Members, and should combine them in the file
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
"pub_key":{
|
"pub_key":{
|
||||||
"type":"AC26791624DE60",
|
"type":"tendermint/PubKeyEd25519",
|
||||||
"value":"<Member 2 public key>"
|
"value":"<Member 2 public key>"
|
||||||
},
|
},
|
||||||
"power":10,
|
"power":10,
|
||||||
@ -103,7 +103,7 @@ from all the Members, and should combine them in the file
|
|||||||
},
|
},
|
||||||
{
|
{
|
||||||
"pub_key":{
|
"pub_key":{
|
||||||
"type":"AC26791624DE60",
|
"type":"tendermint/PubKeyEd25519",
|
||||||
"value":"<Member N public key>"
|
"value":"<Member N public key>"
|
||||||
},
|
},
|
||||||
"power":10,
|
"power":10,
|
||||||
|
@ -1,5 +1,10 @@
|
|||||||
# Tips
|
# Tips
|
||||||
|
|
||||||
|
## Tendermint Tips
|
||||||
|
|
||||||
|
* [Configure Tendermint to create no empty blocks](https://tendermint.com/docs/tendermint-core/using-tendermint.html#no-empty-blocks).
|
||||||
|
* Store the Tendermint data on a fast drive. You can do that by changing [the location of TMHOME](https://tendermint.com/docs/tendermint-core/using-tendermint.html#directory-root) to be on the fast drive.
|
||||||
|
|
||||||
## Refreshing Your Node
|
## Refreshing Your Node
|
||||||
|
|
||||||
If you want to refresh your node back to a fresh empty state, then your best bet is to terminate it and deploy a new machine, but if that's not an option, then you can:
|
If you want to refresh your node back to a fresh empty state, then your best bet is to terminate it and deploy a new machine, but if that's not an option, then you can:
|
||||||
|
Loading…
x
Reference in New Issue
Block a user