AaronFiore/btcpayserver-docker
1
0
Fork 0
Code Activity

Remove legacy pregen docker compose

Browse Source
This commit is contained in:
nicolas.dorier
2018-09-29 21:56:08 +09:00
parent 9acb5d8067
commit 612d8ec6f0
20 changed files with 39 additions and 1671 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
Production/README.md
View File

@@ -1,19 +1,7 @@
# About those docker-compose
# How to use docker-compose with NGinx
All `docker-compose` files in [Production](Production) and [Production-NoReverseProxy](Production-NoReverseProxy) are generated by running the [build-pregen.sh](build-pregen.sh) (or [build-pregen.ps1](build-pregen.ps1)) script from the fragments located in [docker-compose-generator/docker-fragments](docker-compose-generator/docker-fragments).
The pre-generated `docker-compose` files only cover `btc`, `ltc`, `clightning` with `nginx`.
---
We strongly advise you to not use the pre-generated docker-compose of this folder, they are deprecated and kept only for backward compatibility.
Instead use the [build.sh](../build.sh) as documented in (README)(../Readme.md) to generate a docker-compose which fit your needs.
---
The `docker-compose` can be used for production purpose.
It is composed of:
NGinx acts as a reverse proxy, and take care of renewing HTTPS certificates for you.
BTCPay Server deployment using NGinx are typically composed of:
1. One full node per supported cryptocurrency (bitcoind/litecoind)
2. A lightweight block explorer ([NBxplorer](https://github.com/dgarage/NBXplorer))