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
ca561a919e
|
7 years ago | |
---|---|---|
.. | ||
Production.png | 7 years ago | |
README.md | 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:
- A full node (Bitcoin Core)
- 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.
This docker-compose
is used for one click deploy on azure by an Ubuntu, it can be used 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 internetLETSENCRYPT_EMAIL
: The email Let's Encrypt will use to notify you about certificate expiration.BITCOIND_COOKIEFILE
: The relative path to RPC cookie file from bitcoin's data directory. (.cookie
for mainnet,regtest/.cookie
for regtest,testnet3/.cookie
for testnet)BITCOIND_NETWORKPARAMETER
: The blockchain identifier parameter used by bitcoind (regtest=1
for regtest,testnet=1
for testnet,#mainnet=1
for mainnet)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)
Any unset or empty environment variable will be set for a regtest
deployment.