Product-led

Deploy script walkthrough

The guide ships a deploy script so you are not inventing systemd units at 1am. Here is what it is doing, in order, and what to check when it fails.

The AI Trading Bot Guide includes a deploy script so you are not assembling systemd, venv, and env files from memory. This page is the map of that path. Exact filenames ship in the download.

What you should have before you run it

• Ubuntu VPS you can SSH into
• A non-root user with sudo
• API keys ready, withdraw off
• Telegram token and chat ID
• DRY_RUN=true until paper logs are boring

The usual deploy order

1. Copy the project folder to the server.
2. Create the virtualenv and install pinned requirements.
3. Write .env from the template on the server.
4. Run a one-shot health command if the guide includes it.
5. Install the systemd unit.
6. Watch logs for one full scan interval.
7. Confirm a Telegram “up” message.

Environment template (shape, not secrets)

DRY_RUN=true
BINANCE_API_KEY=
BINANCE_API_SECRET=
TELEGRAM_BOT_TOKEN=
TELEGRAM_CHAT_ID=
DAILY_LOSS_LIMIT_USD=10
SCAN_INTERVAL_SEC=300

If a required variable is missing, the process should refuse to start. A silent default of live trading is a bug.

When the script fails

• Permission denied on .env — user mismatch with the systemd unit.
• Module not found — the service is not using the venv ExecStart.
• 401 from Binance — key, IP allowlist, or clock skew.
• No Telegram — token/chat id; outbound 443.

Keep reading