Browse Source
Update daemon startup info in the README
For quite a while already, the daemons need to be started with more elaborate
commands. Point to `start_all.sh` script that shows a working example.
feature/force-stop-button
Mariusz Klochowicz
3 years ago
No known key found for this signature in database
GPG Key ID: 470C865699C8D4D
1 changed files with
3 additions and
16 deletions
-
README.md
|
|
|
@ -26,23 +26,10 @@ The script also enables backtraces by setting `RUST_BACKTRACE=1` env variable. |
|
|
|
|
|
|
|
## Starting the maker and taker daemon |
|
|
|
|
|
|
|
The maker and taker frontend depend on the respective daemon running. |
|
|
|
|
|
|
|
At the moment the maker daemon has to be started first: |
|
|
|
|
|
|
|
```bash |
|
|
|
cargo run --bin maker |
|
|
|
``` |
|
|
|
|
|
|
|
Once the maker is started you can start the taker: |
|
|
|
A working example of starting both daemons with all the required command-line parameters can be found |
|
|
|
[here](https://github.com/itchysats/itchysats/blob/master/start_all.sh#L8) |
|
|
|
|
|
|
|
```bash |
|
|
|
cargo run --bin taker |
|
|
|
``` |
|
|
|
|
|
|
|
Upon startup the taker daemon will connect to the (hardcoded) maker and retrieve the current order. |
|
|
|
|
|
|
|
Note: The sqlite databases for maker and taker are currently created in the project root. |
|
|
|
The maker and taker frontend depend on the respective daemon running. |
|
|
|
|
|
|
|
## Starting the maker and taker frontend |
|
|
|
|
|
|
|
|
