The docker compose running several services for the BTCPay Server community
It contains the following services for the community:
- Slack invite - (slack.btcpayserver.org)
- Mattermost server - (chat.btcpayserver.org)
- Bot which bridge IRC, MatterMost, Slack and Telegram.
- BTCPay Server Web Installer/Configurator - (install.btcpayserver.org)
- Plugin Builder - (plugin-builder.btcpayserver.org)
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.orgWhere:
SLACK_TOKENis your secret slack tokenMATTERMOST_HOSTis the mattermost domain nameBOT_NICKNAMEis the name of the bot on mattermostBOT_PASSis the pass of the bot on mattermostTELEGRAM_TOKENis the telegram tokenCONFIGURATOR_HOSTis the configurator domain nameFIREFLY_HOSTis 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 -dPlease note that previously used docker-compose will now likely fail in setup. So ensure you are consistenly using docker compose without -.
If you need to update the version of a service (e.g., Plugin Builder), follow these steps:
- Update the
docker-compose.ymlfile in the repository and push commit. - On the server, run the following commands:
git pull
docker compose up -dOn 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.
We advise you to change PluginSettings/EnableUploads to true manually (/var/lib/docker/volumes/root_mm-config/_data/config.json).