Zeppelin production environment

Zeppelin's production environment - that is, the bot, API, and dashboard - uses Docker.

Starting the production environment

Install Docker on the machine running the bot
Clone the respository git clone https://github.com/ZeppelinBot/Zeppelin. This creates a new folder called "Zeppelin", and copies the bot's code into the Zeppelin folder.
Enter the Zeppelin folder.
Make a copy of .env.example called .env
Open .env and fill in the missing values.
Run docker compose -f docker-compose.production.yml up -d

Note: The dashboard and API are exposed with a self-signed certificate. It is recommended to set up a proxy with a proper certificate in front of them. Cloudflare is a popular choice here.

Updating the bot

One-click script

If you've downloaded the bot's files by cloning the git repository, you can use update.sh to update the bot.

Manual instructions

Shut the bot down: docker compose -f docker-compose.production.yml stop
Update the files (e.g. git pull)
Start the bot again: docker compose -f docker-compose.production.yml start

Ephemeral hotfixes

If you need to make a hotfix to the bot's source files directly on the server:

Shut the bot down: docker compose -f docker-compose.production.yml stop
Make your edits
Start the bot again: docker compose -f docker-compose.production.yml start

Note that you can't edit the compiled files directly as they're overwritten when the environment starts. Only edit files in /backend/src, /shared/src, and /dashboard/src.

Make sure to revert any hotfixes before updating the bot normally.

View logs

To view real-time logs, run docker compose -f docker-compose.production.yml logs -t -f

1.7 KiB Raw Blame History