AaronFiore/btcpayserver-docker
1
0
Fork 0
Code Activity

Rename to Test to Production-NoReverseProxy

Browse Source
This commit is contained in:
nicolas.dorier
2018-03-20 13:43:31 +09:00
parent acf53c34a7
commit 2ad48fcdd6
6 changed files with 13 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
README.md
View File

@@ -12,14 +12,14 @@ As you can see, it depends on several piece of infrastructure, mainly:
Setting up the dependencies might be time consuming, this repository is meant to give working example of `docker-compose` file which will setup everything for you.
The [Test](Test) `docker-compose` are used for local testing.
The [Production](Production) `docker-compose` are used for production environment. It adds NGinx as a reverse proxy and [Let's Encrypt and DockerGen](https://github.com/gilyes/docker-nginx-letsencrypt-sample) to automatically configure HTTPS.
The [Production](Production) `docker-compose` files are used for production environment. It adds NGinx as a reverse proxy and [Let's Encrypt and DockerGen](https://github.com/gilyes/docker-nginx-letsencrypt-sample) to automatically configure HTTPS.
The production `docker-compose` is used under the hood to deploy an instance of BTCPay on Microsoft Azure in one click:
[![Deploy to Azure](https://azuredeploy.net/deploybutton.svg)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2Fbtcpayserver%2Fbtcpayserver-azure%2Fmaster%2Fazuredeploy.json)
The [Production-NoReverseProxy](Production-NoReverseProxy) `docker-compose` files are used for environment which are already behind a reverse proxy. It exposes BTCPayServer directly on port 80.
# About accessing services inside those docker compose
Several scripts are provided to access the internal of your docker-service.
@@ -32,4 +32,9 @@ You can use it easily:
```
bitcoin-cli.sh getblockcount
```
```
# About generate-docker-compose
The files in `Production` and `Production-NoReverseProxy` are generated by a dotnet program located in `docker-compose-generator`.
It is meant to generate a wide range a configuration from `docker-compose-generator/docker-fragments` without repeating myself.