Przeglądaj źródła

Merge pull request #2362 from nginx-proxy/dependabot/docker/nginxproxy/forego-0.18.1-debian

build: bump nginxproxy/forego from 0.17.3 to 0.18.1
Nicolas Duchon 1 rok temu
rodzic
commit
35c6b2afe5
3 zmienionych plików z 14 dodań i 2 usunięć
  1. 1 1
      Dockerfile.alpine
  2. 1 1
      Dockerfile.debian
  3. 12 0
      docs/README.md

+ 1 - 1
Dockerfile.alpine

@@ -1,6 +1,6 @@
 FROM nginxproxy/docker-gen:0.11.1 AS docker-gen
 
-FROM nginxproxy/forego:0.17.3 AS forego
+FROM nginxproxy/forego:0.18.1 AS forego
 
 # Build the final image
 FROM nginx:1.25.3-alpine

+ 1 - 1
Dockerfile.debian

@@ -1,6 +1,6 @@
 FROM nginxproxy/docker-gen:0.11.1-debian AS docker-gen
 
-FROM nginxproxy/forego:0.17.3-debian AS forego
+FROM nginxproxy/forego:0.18.1-debian AS forego
 
 # Build the final image
 FROM nginx:1.25.3

+ 12 - 0
docs/README.md

@@ -674,6 +674,18 @@ By default the nginx configuration `upstream` blocks will use this block's corre
 
 Please note that using regular expressions in `VIRTUAL_HOST` will always result in a corresponding `upstream` block with an SHA1 name.
 
+### Disabling colors in the log output
+
+To remove colors from the log output, set the [`NO_COLOR` environment variable to any value other than an empty string](https://no-color.org/) on the nginx-proxy container.
+
+```console
+docker run --detach \
+  --publish 80:80 \
+  --env NO_COLOR=1 \
+  --volume /var/run/docker.sock:/tmp/docker.sock:ro \
+  nginxproxy/nginx-proxy
+```
+
 ### Troubleshooting
 
 If you can't access your `VIRTUAL_HOST`, inspect the generated nginx configuration: