Browse Source

Rename to Test to Production-NoReverseProxy

migrate-pregen
nicolas.dorier 7 years ago
parent
commit
2ad48fcdd6
  1. 3
      Production-NoReverseProxy/README.md
  2. 0
      Production-NoReverseProxy/docker-compose.btc-ltc.yml
  3. 0
      Production-NoReverseProxy/docker-compose.btc.yml
  4. 13
      README.md
  5. 0
      docker-compose-generator/docker-fragments/btcpayserver-noreverseproxy.yml
  6. 4
      docker-compose-generator/src/Program.cs

3
Test/README.md → Production-NoReverseProxy/README.md

@ -1,10 +1,11 @@
# About this docker-compose
This `docker-compose` shows how to configure postgres, bitcoind, NBXplorer and BTCPay on regtest.
This `docker-compose` files can be used for production purpose.
![Architecture](https://github.com/btcpayserver/btcpayserver-doc/raw/master/img/Architecture.png)
This is the same architecture as [Production](../Production) but without NGINX as a reverse proxy.
It is suited for environment which already expose the host behind a reverse proxy.
The relevant environment variables are:

0
Test/docker-compose.btc-ltc.yml → Production-NoReverseProxy/docker-compose.btc-ltc.yml

0
Test/docker-compose.btc.yml → Production-NoReverseProxy/docker-compose.btc.yml

13
README.md

@ -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.

0
docker-compose-generator/docker-fragments/btcpayserver-test.yml → docker-compose-generator/docker-fragments/btcpayserver-noreverseproxy.yml

4
docker-compose-generator/src/Program.cs

@ -29,11 +29,11 @@ namespace DockerGenerator
def.Build();
}
var testLocation = FindLocation("Test");
var testLocation = FindLocation("Production-NoReverseProxy");
foreach(var def in defs)
{
def.Fragments.Remove("nginx");
def.Fragments.Add("btcpayserver-test");
def.Fragments.Add("btcpayserver-noreverseproxy");
def.BuildOutputDirectory = testLocation;
def.Build();
}

Loading…
Cancel
Save