version: '3.1' services: php: image: php:7-fpm container_name: ${CONTAINER_PREFIX}_php web: image: nginx depends_on: - php restart: always container_name: ${CONTAINER_PREFIX}_web volumes: - ${DATA_ROOT}/conf/nginx.conf:/etc/nginx/conf.d/default.conf - ${DATA_ROOT}/logs:/var/log/nginx - ${DATA_ROOT}/www:/var/www/html ports: # the router forwards internet traffic from 80 to the host # machine where "web" is listening on exposed port 8080 # the request will be processed according to the # configurations in nginx.conf - 8280:80 https-portal: image: steveltn/https-portal:1 container_name: ${CONTAINER_PREFIX}_https-portal ports: #- 8080:80 # the router forwards internet traffic from 443 to the host # machine where https-portal is listening on 443 - 8080:80 - 443:443 depends_on: - web restart: always volumes: - ${DATA_ROOT}/ssl_certs:/var/lib/https-portal environment: # DOMAINS: 'dav.algometic.com->http://vsu-koala:80 #local, # www.vortifytech.com-> http://web:80 #production, # cal.algometic.com->http://vsu-koala:80 #local, # algometic.com->http://vsu-dolphin:80 #staging' # DOMAINS: ' # algometic.com=>www.algometic.com, # www.algometic.com->http://vorsprung.local:8280 #production, # mango.algometic.com->http://vorsprung.local:8111 #production, # ocd.algometic.com->http://vorsprung.local:1234 #production, # code.algometic.com->http://vorsprung.local:9980 #production, # 58985620.algometic.com->http://vorsprung.local:8055 #production, # melody.algometic.com->http://vorsprung.local:9045 #production, # metrics.algometic.com->http://vorsprung.local:3000 #production, # books.algometic.com->http://vorsprung.local:8783 #production, # syn.algometic.com->http://vorsprung.local:9081 #production, # slot.algometic.com->http://vorsprung.local:9981 #production, # slot1234.algometic.com->http://vorsprung.local:1235 #production, # ' # # if you are getting a 502 bad gateway error (111:connection refused) while # connecting to upstream, verify the redirection actually is accessible from # within https-portal to the destination. # For instance, specifying the hostname vorsprung without the .local # domain name resolves to 127.0.0.1, which of course wouldn't work because # the service is not running on https-portal. The proper fix is to # use vorspurng.local which resolves to 192.168.1.124 # # # jupyter.algometic.com->http://vorsprung.local:8564 #production, # algometic.com=>www.algometic.com, # 1984.algometic.com->192.168.6.10:8118 #production, DOMAINS: ' algometic.com->http://vorsprung.local:8280 #production, www.algometic.com->http://vorsprung.local:8280 #production, mango.algometic.com->http://vorsprung.local:8111 #production, ocd.algometic.com->http://vorsprung.local:1235 #production, code.algometic.com->http://vorsprung.local:9981 #production, 58985620.algometic.com->http://vorsprung.local:8055 #production, melody.algometic.com->http://vorsprung.local:9045 #production, metrics.algometic.com->http://vorsprung.local:3000 #production, books.algometic.com->http://vorsprung.local:8783 #production, syn.algometic.com->http://vorsprung.local:9081 #production, git.algometic.com->http://vorsprung.local:3079 #production, element.algometic.com->http://vorsprung.local:8008 #production, matrix.algometic.com->http://vorsprung.local:8380 #production, identity.algometic.com->http://vorsprung.local:8090 #production, cine.algometic.com->http://vorsprung.local:8096 #production, hub.algometic.com->192.168.1.118:8099 #production, 3ds.algometic.com->192.168.1.118:5123 #production, ' # #algometic.com->http://vsu-dolphin:80 #local, CLIENT_MAX_BODY_SIZE: 64M