diff --git a/README.md b/README.md index 9fa753f..95b6d6d 100644 --- a/README.md +++ b/README.md @@ -163,6 +163,7 @@ Available `BTCPAYGEN_ADDITIONAL_FRAGMENTS` currently are: * [opt-add-tor-relay](docker-compose-generator/docker-fragments/opt-add-tor-relay.yml), for a non-exit tor relay. Make sure to have ports 9001 and 9030 accessible externally. [Please read the legal implications of running a tor relay](https://www.eff.org/torchallenge/faq.html) and [what resources are used to operate the relay](https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#RelayRequirements). * [opt-add-electrumx](docker-compose-generator/docker-fragments/opt-add-electrumx.yml), to integrate a full ElectrumX server (from official source) with BTCPay, using the BTCPay server's full bitcoin node for complete privacy when using your own Electrum wallet. You can also open port 50002 up to the internet on your router etc, to be part of the ElectrumX network, helping other Electrum wallet users to get connected. The bitcoin option `-txindex` is mandatory for ElectrumX, and this fragement will enable it on your BTCPay server automatically - NO need to use the fragment opt-txindex.yml. * [opt-add-electrum-ps](docker-compose-generator/docker-fragments/opt-add-electrum-ps.yml), to integrate Electrum Personal Server (EPS) with BTCPay (EPS is a single-user alternative to the ElectrumX Server option above). EPS will also use the BTCPay server's full bitcoin node for complete privacy when using your own Electrum wallet, for your own personal use (i.e. other users cannot use your server to verify transactions). Also, the bitcoin option `-txindex` is NOT mandatory for EPS, and it will run on a pruned node (unlike ElectrumX). You will need to add your XPUB/YPUB/ZPUB as environment variable `EPS_XPUB` before enabling EPS for the first time (see above section on environment variables, and see [full documentation](https://github.com/btcpayserver/btcpayserver-doc/blob/master/ElectrumPersonalServer.md) for details). +* [opt-add-configurator](docker-compose-generator/docker-fragments/opt-add-configurator.yml), to integrate the [BTCPay Server Configurator](https://install.btcpayserver.org) to manage your BTCPay deployment through a UI, and to allow new deployments elsewhere easily. You can also create your own [custom fragments](#how-can-i-customize-the-generated-docker-compose-file). diff --git a/docker-compose-generator/docker-fragments/opt-add-configurator.yml b/docker-compose-generator/docker-fragments/opt-add-configurator.yml index 4da2980..4623d49 100644 --- a/docker-compose-generator/docker-fragments/opt-add-configurator.yml +++ b/docker-compose-generator/docker-fragments/opt-add-configurator.yml @@ -3,7 +3,7 @@ version: "3" services: configurator: restart: unless-stopped - image: btcpayserver/btcpayserver-configurator:0.0.18 + image: btcpayserver/btcpayserver-configurator:0.0.19 environment: CONFIGURATOR_SSHCONNECTION: "root@host.docker.internal" CONFIGURATOR_SSHKEYFILE: ${BTCPAY_SSHKEYFILE}