From 5e592bb25bd528909eb9bc0949e519fc8df2360b Mon Sep 17 00:00:00 2001 From: jholdstock Date: Fri, 31 Jul 2020 09:56:30 +0100 Subject: [PATCH] Update disaster recovery docs Mention that wallets can be recovered automatically now that the consistency checking code is merged. --- docs/deployment.md | 26 +++++++++++++++----------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/docs/deployment.md b/docs/deployment.md index 88657bc..5e79160 100644 --- a/docs/deployment.md +++ b/docs/deployment.md @@ -27,7 +27,7 @@ servers hosting these wallets should ideally be in geographically seperate locations. Each voting server should be running an instance of dcrd and dcrwallet. The -wallet on these servers should be completely empty and not used of any other +wallet on these servers should be completely empty and not used for any other purpose. dcrwallet should be permenantly unlocked and have voting enabled (`--enablevoting`). vspd on the front-end server must be able to reach each instance of dcrwallet over RPC. @@ -141,20 +141,24 @@ the admin page of the vspd web front-end. ## Disaster Recovery -The database file contains everything needed to restore a vspd deployment - -simply place the database file into the vspd data directory and start vspd as -normal. +### Voting Wallets - +The vspd database file contains everything needed to restore a vspd deployment +from scratch. Simply place the database file into the vspd data directory and +start vspd as normal. vspd will use the database to insert all necessary data +into all of the voting wallets. ## Listing on decred.org