banbot allows you to perform real-time simulated trading or live trading without modifying your strategies.

Deploying the Trading Bot

1. Compilation

Compiling from WebUI
You can execute bot to start the WebUI directly, then navigate to /en-US/setting/. On the left side, select 【Compile Code】, and on the right side, choose the target system and architecture. Proceed with the compilation and download.

Compiling from Terminal
Possible values for GOOS: linux, darwin, windows, ...
Possible values for GOARCH: amd64, arm64, ...

Linux/MacOS

export GOARCH="amd64"
export GOOS="linux"
go build -o bot

Windows Power Shell

# build for windows
$env:GOARCH="amd64"
$env:GOOS="windows"
go build -o bot.exe

# build for linux
$env:GOARCH="amd64"
$env:GOOS="linux"
go build -o bot

Windows CMD

# build for windows
set GOARCH=amd64
set GOOS=windows
go build -o bot.exe

# build for linux
set GOARCH=amd64
set GOOS=linux
go build -o bot

2. Preparing the Database

Install and start TimeScaledb. It is recommended to use Docker for a quick setup. Refer to the documentation.

Save your database connection string: postgresql://postgres:123@[host.docker.internal]:5432/ban (You may need to modify the password or database name, etc.)

Note

You do not need to create the database or related table structures. banbot will automatically initialize the database and related table structures upon startup.

3. Editing Configuration

Upload the compiled executable file to the /ban directory on the target server. Create a directory /ban/data as the data directory and set the environment variable BanDataDir=/ban/data.

Then execute /ban/bot init to generate a YML configuration file in /ban/data.

Next, edit the /ban/data/config.local.yml file to set the database connection string, exchange keys, single transaction amount, trading strategy, and cycle, etc.

You can configure multiple strategies and accounts. If you need to run multiple strategies on different accounts, you can create multiple YML configuration files and start multiple bot processes accordingly.

For detailed configuration, refer to the Configuration File.

Note

config.local.yml takes precedence over config.yml. You can modify your configuration in either of these files. There is no need to specify these configuration file paths during startup; they will be automatically read.

4. Starting the Trading Bot

You need to start both the spider process and the bot process. The spider process is used to subscribe to and update public data such as candlestick charts and order books, saving them to the database. The bot process subscribes to candlestick data and other information from the spider process and executes trading strategies. You can start multiple bot processes to run different strategies.

Strategies and trading accounts consume minimal resources. On a 2-core, 2GB VPS, you can start dozens of bot processes, each configured with hundreds of strategies and trading accounts.

Starting the Spider
Execute bot spider to start the spider process immediately. It is recommended to start it in the background and dump the logs:

nohup /ban/bot spider > /tmp/spider.log 2>&1 &

Starting the Trading Bot
Execute bot trade to start the real-time trading bot. It is recommended to start it in the background and dump the logs:

nohup /ban/bot trade -config $demo.yml > /tmp/trade.log 2>&1 &

Tip

The logs for the spider process will be automatically saved to $logs/spider.log; the logs for the bot process will be automatically saved to $logs/[bot_name].log. Log files will be rotated automatically when they exceed 300MB in size.

Therefore, you can directly redirect the stdout and stderr of both the spider and the bot to /dev/null.

5. Notifications, DashBoard, and Monitoring

Notifications
You can configure rpc_channels in the YML file for notifications. Messages will be sent to your social apps (currently supporting WeCom) when the bot starts, stops, enters a position, or exits a position.

You can follow the WeCom plugin in WeChat (scan the QR code from the WeCom PC management console) to receive these messages in WeChat.

DashBoard

You can configure api_server in the yml file, which will start a web service simultaneously when the robot is started. Then you can access the robot's DashBoard through the configured account and password after the robot is started, to view the trading overview and manage the robot.

The web service above is started with http, it is recommended that you set bind_ip to local or LAN ip to avoid unauthorized access.

If you need to access the Dashboard from other hosts, you can connect to the server running the robot via ssh, and then map the web service port to other hosts through port forwarding:

ssh -L [local port]:[remote host]:[remote port] [username]@[remote server address]
# e.g.
ssh -L 8001:127.0.0.1:8001 your_username@remote_server_address

Tip

If you need to expose the dashboard to the Internet, it is strongly recommended that you configure https through nginx and set a strong account and password.

Monitoring
You can use crontab to periodically execute the check_bot.sh script to check the bot's status and send email notifications.

# for centos 8
dnf install mailx
vi /etc/mail.rc

Sample configuration:

set smtp=smtps://smtp.gmail.com:465
set smtp-auth=login
set smtp-auth-user=your_email@gmail.com
set from=your_email@gmail.com
set smtp-auth-password=your_email_password
set ssl-verify=ignore

Test the email sending function:

echo "Test email body" | mail -s "Test email subject" recipient@example.com

Open crontab:

crontab -e

Add a line:

*/5 * * * * /ban/check_bot.sh trade user1@example.com user2@example.com

Grant execution permissions to the script:

chmod +x /ban/check_bot.sh