olli/dabo
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

documentation

Browse Source
This commit is contained in:
olli 2023-05-09 12:04:13 +02:00
parent b6a515774d
commit bc841f271d
2 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
README.md
View File

@ -45,9 +45,12 @@ I thought this fits quite well to the cryptotrading world and that's why i chose
Linux knowledge required! Linux knowledge required!
Needed a running Docker install. Traefik suggested, see Needed a running Docker install. Traefik suggested, see
https://gitea.ds9.dedyn.io/olli/debian.ansible.docker https://gitea.ds9.dedyn.io/olli/debian.ansible.docker
https://gitea.ds9.dedyn.io/olli/debian.ansible.traefik.server https://gitea.ds9.dedyn.io/olli/debian.ansible.traefik.server
Download: Download:
``` ```
git clone https://gitea.ds9.dedyn.io/olli/dabo.git git clone https://gitea.ds9.dedyn.io/olli/dabo.git
@ -59,11 +62,6 @@ Build container:
docker -l warn compose --ansi never build --progress=plain --pull --no-cache --force-rm docker -l warn compose --ansi never build --progress=plain --pull --no-cache --force-rm
``` ```
Set Rights (UID 10000 for non-root-User in running container):
```
chown -R 10000:10000 dabo data home
```
Edit docker-compose.yml or create docker-compose.override.yml to fit yout needs e.g. domain and network settings or basic auth, e.g. for traefik and letsencrypt: Edit docker-compose.yml or create docker-compose.override.yml to fit yout needs e.g. domain and network settings or basic auth, e.g. for traefik and letsencrypt:
``` ```
echo ' echo '
@ -108,7 +106,9 @@ networks:
Optional: If you use signal-cli (https://gitea.ds9.dedyn.io/olli/debian.ansible.signal-cli.client) and want do receive Signal-Messages from the bot you can create an SSH-Key to allow sending Signal-Messages e.g.: Optional: If you use signal-cli (https://gitea.ds9.dedyn.io/olli/debian.ansible.signal-cli.client) and want do receive Signal-Messages from the bot you can create an SSH-Key to allow sending Signal-Messages e.g.:
``` ```
mkdir -p home/.ssh
ssh-keygen -f home/.ssh/id_ed25519 -N "" -t ed25519 ssh-keygen -f home/.ssh/id_ed25519 -N "" -t ed25519
chmod 700 home/.ssh
cat home/.ssh/id_ed25519.pub cat home/.ssh/id_ed25519.pub
``` ```
and add Key on your signal-cli-Server to the authorized_keys of the signal-User and add Key on your signal-cli-Server to the authorized_keys of the signal-User
@ -118,13 +118,14 @@ Create Secrets file for your API Key(s)
``` ```
# for Bitpanda # for Bitpanda
echo 'local API_TOKEN=YOUR_VERY_LOOOOOOONNNNGGGG_API_TOKEN_FROM_BITPANDA' >dabo/.bitpanda-secrets echo 'local API_TOKEN=YOUR_VERY_LOOOOOOONNNNGGGG_API_TOKEN_FROM_BITPANDA' >dabo/.bitpanda-secrets
chmot 400 dabo/.bitpanda-secrets
# or for Binance # or for Binance
echo 'local API_SECRET="YOUR_LONG_API_SECRET_FROM_BINANCE" echo 'local API_SECRET="YOUR_LONG_API_SECRET_FROM_BINANCE"
local API_KEY="YOUR_LONG_API_KEY_FROM_BINANCE" '>dabo/.binance-secrets local API_KEY="YOUR_LONG_API_KEY_FROM_BINANCE" '>dabo/.binance-secrets
chmod 400 dabo/.binance-secrets
``` ```
Edit your Config Edit your Config
Especially change URL, STOCK_EXCHANGE, FEE, CURRENCY,... to fit your needs. Especially change URL, STOCK_EXCHANGE, FEE, CURRENCY,... to fit your needs.
``` ```
@ -137,6 +138,13 @@ Prepare/Create a stretegy
IMPORTANT!!! THE DEFAULT STRATEGY MAY NOT FIT YOUR NEEDS OR WORK FPR YOU PROPERLY. SO YOU CAN LOOSE ALL YOUR MONEY!!! USE ON YOUR OWN RISK!!! IMPORTANT!!! THE DEFAULT STRATEGY MAY NOT FIT YOUR NEEDS OR WORK FPR YOU PROPERLY. SO YOU CAN LOOSE ALL YOUR MONEY!!! USE ON YOUR OWN RISK!!!
Set Rights (UID 10000 for non-root-User in running container):
```
chown -R 10000:10000 dabo data home
```
Run/Restart: Run/Restart:
``` ```
docker-compose down # if an old instance is running docker-compose down # if an old instance is running

2
dabo/dabo-bot.conf
View File

@ -1,6 +1,6 @@
# Webpage URL # Webpage URL
URL="dabo.ds9.dedyn.io" URL="dabo-bitpanda.ds9.dedyn.io"
# The exchange we use for using the correct API (BINANCE or BITPANDA) # The exchange we use for using the correct API (BINANCE or BITPANDA)
STOCK_EXCHANGE="BITPANDA" STOCK_EXCHANGE="BITPANDA"