kylefang/stacks-node-mainnet
1
0
Fork 0
mirror of https://github.com/alexgo-io/stacks-node-mainnet.git synced 2026-01-12 14:53:47 +08:00
Code Issues Packages Projects Releases Wiki Activity

chore: update README for restoring backup

Browse Source
This commit is contained in:
Yuanhai He
2023-05-26 09:03:44 +00:00
parent 9b431b51ea
commit 40a3aecf88
1 changed files with 6 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -9,6 +9,8 @@ Note: **use `stop.sh` to shutdown daemons!**
## How to spin up a stacks-node from cold backup
This is easiest and recommended way. The only caveat is the fixed password for postgres user. As long as you keep the firewall rejecting connections to postgres server, this won't be an issue; otherwise you'll have to change the password after restoring from backup and update the password configuration in `docker-compose.yml` accordingly.
The scripts are tested on debian 11. Clone this repo and follow the steps.
1. Run ./setup.sh and reboot the server
@@ -19,14 +21,14 @@ The scripts are tested on debian 11. Clone this repo and follow the steps.
## How to spin up a stacks-node from archive
The scripts works on debian 11. And always check if you're using the latest versions in `docker-compose.yml`.
The scripts are tested on debian 11. Remember to check if you're using the latest versions in `docker-compose.yml` before following the steps below.
```bash
# prerequisites
./setup.sh
```
Start 2 terminals to restore stacks node and postgres.
Start 2 terminals to restore stacks node and postgres, this will take a long time.
```bash
# terminal 1
@@ -47,8 +49,8 @@ Check if everything works.
docker-compose logs -f
```
Check if blocks catch up with official node: `https://api.hiro.so/v2/info`
Wait until the block height catches up with official node: `https://api.hiro.so/v2/info`
```bash
curl http://127.0.0.1:20443/v2/info
watch 'curl -s http://127.0.0.1:3999/extended/v1/status'
```