1
0

Can configure LIGHTNING_ALIAS

This commit is contained in:
nicolas.dorier
2018-03-22 00:11:38 +09:00
parent 7e306323f0
commit 23f2e4eaad
10 changed files with 12 additions and 0 deletions

View File

@@ -21,6 +21,7 @@ The relevant environment variables are:
* `BTCPAY_HOST`: the external url used to access the NGINX server from internet. This domain name must point to this machine for Let's Encrypt to create your certificate. (typically with a CNAME or A record)
* `LETSENCRYPT_EMAIL`: The email Let's Encrypt will use to notify you about certificate expiration.
* `ACME_CA_URI`: Let's encrypt API endpoint (`https://acme-staging.api.letsencrypt.org/directory` for a staging certificate, `https://acme-v01.api.letsencrypt.org/directory` for a production one)
* `LIGHTNING_ALIAS`: Optional, if using the integrated lightning feature, customize the alias of your nodes
Use `docker-compose.btc-ltc.yml` for bitcoin and litecoin support, or `docker-compose.btc.yml` for only bitcoin.

View File

@@ -116,6 +116,7 @@ services:
bitcoin-rpcconnect=bitcoind
ipaddr=${BTCPAY_HOST}
network=${NBITCOIN_NETWORK:-regtest}
alias=${LIGHTNING_ALIAS:-}
chain=btc
volumes:
- "clightning_bitcoin_datadir:/root/.lightning"

View File

@@ -124,6 +124,7 @@ services:
bitcoin-rpcconnect=litecoind
ipaddr=${BTCPAY_HOST}:9736
network=${NBITCOIN_NETWORK:-regtest}
alias=${LIGHTNING_ALIAS:-}
chain=ltc
volumes:
- "clightning_litecoin_datadir:/root/.lightning"
@@ -157,6 +158,7 @@ services:
bitcoin-rpcconnect=bitcoind
ipaddr=${BTCPAY_HOST}
network=${NBITCOIN_NETWORK:-regtest}
alias=${LIGHTNING_ALIAS:-}
chain=btc
volumes:
- "clightning_bitcoin_datadir:/root/.lightning"

View File

@@ -116,6 +116,7 @@ services:
bitcoin-rpcconnect=litecoind
ipaddr=${BTCPAY_HOST}:9736
network=${NBITCOIN_NETWORK:-regtest}
alias=${LIGHTNING_ALIAS:-}
chain=ltc
volumes:
- "clightning_litecoin_datadir:/root/.lightning"