You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
nicolas.dorier
c689f7939d
|
7 years ago | |
---|---|---|
.. | ||
Production.png | 7 years ago | |
README.md | 7 years ago | |
docker-compose.btc-ltc.yml | 7 years ago | |
docker-compose.btc.yml | 7 years ago | |
docker-compose.yml | 7 years ago | |
nginx.tmpl | 7 years ago |
README.md
About this docker-compose
The docker-compose
can be used for production purpose.
It is composed of:
- One full node per supported cryptocurrency (bitcoind/litecoind)
- A lightweight block explorer (NBxplorer)
- A BTCPay Server
- A database (Postgres)
- A reverse proxy (NGINX)
- Two containers configuring NGINX as a reverse proxy and renewing SSL certificates.
The Deploy on Azure Button is using this docker-compose
under the hood on an Ubuntu machine. You can use it on any docker supporting host.
The relevant environment variables are:
NBITCOIN_NETWORK
: the blockchain identifier used by NBitcoin (eg.,regtest
,testnet
,mainnet
)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)
Use docker-compose.btc-ltc.yml
for bitcoin and litecoin support, or docker-compose.btc.yml
for only bitcoin.
Any unset or empty environment variable will be set for a regtest
deployment.