Merge pull request #30 from mbio16/docker-compose-own-reverse-proxy

Docker compose own reverse proxy

docker-compose-own-reverse-proxy.yml

@@ -0,0 +1,48 @@
+version: '3'
+services:
+  boltcard:
+    build: 
+      context: ./
+      dockerfile: Dockerfile
+    container_name: boltcard_main
+    depends_on:
+      - db
+    restart: unless-stopped
+    environment:
+      - LOG_LEVEL=DEBUG
+      - DB_HOST=db
+      - DB_USER=cardapp
+      - DB_PASSWORD=${DB_PASSWORD}
+      - DB_PORT=5432    
+      - DB_NAME=card_db
+    expose: 
+      - "9000"
+    ports:
+      - "8080:9000"
+    volumes:
+      - ${PWD}/tls.cert:/boltcard/tls.cert
+      - ${PWD}/admin.macaroon:/boltcard/admin.macaroon
+    networks:
+      - boltnet
+  db:
+    image: postgres
+    container_name: boltcard_db
+    restart: unless-stopped
+    environment:
+      - POSTGRES_USER=cardapp
+      - POSTGRES_PASSWORD=${DB_PASSWORD}
+      - POSTGRES_DB=card_db
+      - PGDATA=/var/lib/postgresql/data/pgdata
+    volumes:
+      - db-data:/var/lib/postgresql/data
+      - ./select_db.sql:/docker-entrypoint-initdb.d/select_db.sql
+      - ./create_db.sql:/docker-entrypoint-initdb.d/create_db.sql
+      - ./settings.sql:/docker-entrypoint-initdb.d/settings.sql
+    expose:
+      - "5432"
+    networks:
+      - boltnet
+networks:
+  boltnet:
+volumes:
+  db-data:

docs/DOCKER_INSTALL.md

@@ -28,6 +28,15 @@ $ docker volume create caddy_data
 $ docker compose up
 ```
 
+### run boltcard server with own reverse proxy
+If you already have reverse proxy in your enviroment which controls/terminates TLS connections, Boltcard server wont be ready to use, because of existence of own reverse proxy (Caddy). Caddy wont be abble to obtain TLS certificate for your domain name. Run different docker-compose, that will start Boltcard server without Caddy and your reverse proxy will handle TLS.
+
+```
+// add -d option for detached mode
+$ docker-compose up -f docker-compose-own-reverse-proxy.yml
+```
+
+
 ### stop docker
 ```
 $ docker compose down