From a2d1d78e233adb21c6db16c4487f66f2a5ede2fb Mon Sep 17 00:00:00 2001 From: Greg Heartsfield Date: Sat, 6 May 2023 14:42:59 -0500 Subject: [PATCH] docs: reformatting --- docs/reverse-proxy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reverse-proxy.md b/docs/reverse-proxy.md index 157ba5c..c5e0c14 100644 --- a/docs/reverse-proxy.md +++ b/docs/reverse-proxy.md @@ -120,7 +120,7 @@ Assumptions: * `Traefik` is running in `Docker`, using `docker compose` and labels for the static configuration. An equivalent setup useing a Traefik config file is possible too (but not covered here). * Strict Transport Security is enabled. * Hostname for the relay is `relay.example.com`, email adres for ACME certificates provider is `name@example.com`. -* ipv6 is enabled, a viable private ipv6 subnet is specified in the example below. +* ipv6 is enabled, a viable private ipv6 subnet is specified in the example below. * Relay is running on port `8080`. ``` @@ -196,4 +196,4 @@ services: ### Traefik Notes -Traefik will take care of the provisioning and renewal of certificates. In case of an ipv4-only relay, simply detele the `enable_ipv6:` and `ipam:` entries in the `networks:` section of the docker-compose file. \ No newline at end of file +Traefik will take care of the provisioning and renewal of certificates. In case of an ipv4-only relay, simply detele the `enable_ipv6:` and `ipam:` entries in the `networks:` section of the docker-compose file.