[BREAKGLASS] The docker compose running several services for the BTCPay Server community
Go to file
2026-05-04 22:19:29 +09:00
.gitattributes Init commit 2019-01-22 09:14:14 +00:00
.gitignore add configurator 2020-01-11 10:12:14 +01:00
delete-spammer.sh trim spaces in username 2022-08-04 17:37:43 +09:00
docker-compose.yml Update configurator image version to 0.0.28 2026-05-04 22:19:29 +09:00
matterbridge.template.toml Remove gitter 2023-09-04 08:05:45 +09:00
nginx.tmpl update deny 2022-02-02 14:09:18 +09:00
README.md Update README.md to fix legacy docker-compose 2025-05-31 10:57:37 -05:00
update-mattermost.sh Remove gitter from readme 2023-09-04 08:16:54 +09:00

btcpayserver-infra

The docker compose running several services for the BTCPay Server community

It contains the following services for the community:

How to use

Create a .env file with the following content:

SLACK_TOKEN=xoxp-secret-token
MATTERMOST_HOST=chat.btcpayserver.org
CONFIGURATOR_HOST=install.btcpayserver.org
TELEGRAM_TOKEN=...
FIREFLY_HOST=firefly.btcpayserver.org

Where:

  • SLACK_TOKEN is your secret slack token
  • MATTERMOST_HOST is the mattermost domain name
  • BOT_NICKNAME is the name of the bot on mattermost
  • BOT_PASS is the pass of the bot on mattermost
  • TELEGRAM_TOKEN is the telegram token
  • CONFIGURATOR_HOST is the configurator domain name
  • FIREFLY_HOST is the our firefly domain name

This assume that MATTERMOST_HOST, and CONFIGURATOR_HOST are pointing to your server.

Then you can run:

./update-mattermost.sh
docker compose up -d

Please note that previously used docker-compose will now likely fail in setup. So ensure you are consistenly using docker compose without -.

Updating Services

If you need to update the version of a service (e.g., Plugin Builder), follow these steps:

  1. Update the docker-compose.yml file in the repository and push commit.
  2. On the server, run the following commands:
git pull
docker compose up -d

On legacy servers, using new docker compose instead of docker-compose, you may get a warning that volume already exists, but that shouldn't be a problem. We will add a guide on migrating to remove the warning as we further improve the repository.

Additional settings

We advise you to change PluginSettings/EnableUploads to true manually (/var/lib/docker/volumes/root_mm-config/_data/config.json).