nginx-proxy/test/test_acme-http-challenge-location/test_acme-http-challenge-location-legacy.yml

services:
  nginx-proxy:
    environment:
      ACME_HTTP_CHALLENGE_LOCATION: "legacy"

  web1:
    image: web
    expose:
      - "81"
    environment:
      WEB_PORTS: "81"
      VIRTUAL_HOST: "web1.nginx-proxy.tld"

  web2:
    image: web
    expose:
      - "82"
    environment:
      WEB_PORTS: "82"
      VIRTUAL_HOST: "web2.nginx-proxy.tld"
      HTTPS_METHOD: noredirect
feat: variable ACME_HTTP_CHALLENGE_LOCATION (#2468) Values: * `legacy` (default): generate location blocks for ACME HTP Challenge excepted when `HTTPS_METHOD=noredirect` or there is no certificate for the domain * `true`: generate location blocks for ACME HTP Challenge in all cases * `false`: do not generate location blocks for ACME HTP Challenge This feature is currently needed because acme-companion may generate the HTTP Challenge configuration while it was done already by nginx-proxy (see #2465#issuecomment-2136361373). Also sometimes a hardcoded ACME challenge location is not wanted because the challenge validation is not done with acme-companion / Let's Encrypt, and with a challenge location setup differently. 2024-05-31 00:10:44 +02:00			`services:`
tests: factor out base nginx-proxy config 2024-12-30 11:59:07 +01:00			`nginx-proxy:`
			`environment:`
			`ACME_HTTP_CHALLENGE_LOCATION: "legacy"`

feat: variable ACME_HTTP_CHALLENGE_LOCATION (#2468) Values: * `legacy` (default): generate location blocks for ACME HTP Challenge excepted when `HTTPS_METHOD=noredirect` or there is no certificate for the domain * `true`: generate location blocks for ACME HTP Challenge in all cases * `false`: do not generate location blocks for ACME HTP Challenge This feature is currently needed because acme-companion may generate the HTTP Challenge configuration while it was done already by nginx-proxy (see #2465#issuecomment-2136361373). Also sometimes a hardcoded ACME challenge location is not wanted because the challenge validation is not done with acme-companion / Let's Encrypt, and with a challenge location setup differently. 2024-05-31 00:10:44 +02:00			`web1:`
			`image: web`
			`expose:`
			`- "81"`
			`environment:`
			`WEB_PORTS: "81"`
			`VIRTUAL_HOST: "web1.nginx-proxy.tld"`

			`web2:`
			`image: web`
			`expose:`
			`- "82"`
			`environment:`
			`WEB_PORTS: "82"`
			`VIRTUAL_HOST: "web2.nginx-proxy.tld"`
			`HTTPS_METHOD: noredirect`