stakey/vspd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Remove dcrstakepool note. (#370)

Browse Source 
No need to keep the instructions for deploying vspd along dcrstakepool as it is now defunct.
This commit is contained in:
Jamie Holdstock 2023-02-24 14:54:56 +00:00 committed by GitHub
parent 31a2726578
commit 2c1bb0027f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/deployment.md
View File

@ -101,24 +101,6 @@ vspd. **Do not run a voting wallet on your webserver.**
1. Once the database is initialized, vspd can be started for normal operation by 1. Once the database is initialized, vspd can be started for normal operation by
running it without the `--feexpub` flag. running it without the `--feexpub` flag.
## Deploying alongside dcrstakepool
It is possible to run vspd on the same infrastructure as an existing
dcrstakepool deployment.
- On the voting servers...
- The existing dcrd instance requires no changes.
- Create a new instance of dcrwallet listening for RPC connections on a
different port. Ensure the new wallet is unlocked and voting is enabled
(dcrstakepool wallet should still have voting disabled).
- On the front-end server...
- Run an instance of dcrd with txindex enabled.
- Run the vspd binary
- Configure webserver to proxy requests from the internet to vspd.
- Configure vspd to use the newly created dcrwallet instances.
- Web requests for `/api/v3` should be redirected to vspd.
## Monitoring ## Monitoring
A monitoring system with alerting should be pointed at vspd and tested/verified A monitoring system with alerting should be pointed at vspd and tested/verified