stuff
This commit is contained in:
commit
896f2b76aa
204 changed files with 4845 additions and 0 deletions
32
bisq_arbitrage_notes/designs/bisq_daemon.md
Normal file
32
bisq_arbitrage_notes/designs/bisq_daemon.md
Normal file
|
|
@ -0,0 +1,32 @@
|
|||
# Bisq Daemon
|
||||
|
||||
|
||||
The bisq daemon is the daemon bisq client that interacts with the bisq network. It is developed by the bisq DAO, not by the bas team. We simply grab it as it is and deploy it, with backups and monitoring to ensure the best operation.
|
||||
|
||||
## Repo
|
||||
|
||||
All the code necessary to deploy, monitor and backup a bas bisq daemon instance.
|
||||
|
||||
## Deploy
|
||||
|
||||
The bisq daemon is deployed by downloading the already-built daemon executable that gets packaged along bisq's releases.
|
||||
|
||||
|
||||
## Backup
|
||||
|
||||
The data folder gets backed-up in real time via syncthing with oli.
|
||||
|
||||
|
||||
## Monitoring
|
||||
|
||||
The daemon is monitored by running the following command in cron in the daemon's host:
|
||||
|
||||
```bash
|
||||
bisq_cli getversion && curl http://git.contrapeso.xyz:3001/api/push/5rs4qsvNPw?msg=OK&ping=
|
||||
```
|
||||
|
||||
If a ping is not received within a 120 seconds window, a monitoring notification is sent.
|
||||
|
||||
|
||||
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue