From 60f69d56d5709db640531b148d5d1947163a96ca Mon Sep 17 00:00:00 2001 From: Francis Lavoie Date: Fri, 11 Mar 2022 15:05:11 -0500 Subject: [PATCH] review --- src/docs/markdown/api.md | 66 ++++++++++++++-------------- src/docs/markdown/automatic-https.md | 2 +- 2 files changed, 34 insertions(+), 34 deletions(-) diff --git a/src/docs/markdown/api.md b/src/docs/markdown/api.md index b56bdfe..7607a5b 100644 --- a/src/docs/markdown/api.md +++ b/src/docs/markdown/api.md @@ -96,33 +96,33 @@ Export entire config and pretty-print it:
curl "http://localhost:2019/config/" | jq
 {
-  "apps": {
-    "http": {
-      "servers": {
-        "myserver": {
-          "listen": [
-            ":443"
-          ],
-          "routes": [
-            {
-              "match": [
-                {
-                  "host": [
-                    "example.com"
-                  ]
-                }
-              ],
-              "handle": [
-                {
-                  "handler": "file_server"
-                }
-              ]
-            }
-          ]
-        }
-      }
-    }
-  }
+	"apps": {
+		"http": {
+			"servers": {
+				"myserver": {
+					"listen": [
+						":443"
+					],
+					"routes": [
+						{
+							"match": [
+								{
+									"host": [
+										"example.com"
+									]
+								}
+							],
+							"handle": [
+								{
+									"handler": "file_server"
+								}
+							]
+						}
+					]
+				}
+			}
+		}
+	}
 }
Export just the listener addresses: @@ -244,12 +244,12 @@ Returns information about a particular [PKI app](/docs/json/apps/pki/) CA by its
curl "http://localhost:2019/pki/ca/local" | jq
 {
-  "id": "local",
-  "name": "Caddy Local Authority",
-  "root_common_name": "Caddy Local Authority - 2022 ECC Root",
-  "intermediate_common_name": "Caddy Local Authority - ECC Intermediate",
-  "root_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... gRw==\n-----END CERTIFICATE-----\n",
-  "intermediate_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... FzQ==\n-----END CERTIFICATE-----\n"
+	"id": "local",
+	"name": "Caddy Local Authority",
+	"root_common_name": "Caddy Local Authority - 2022 ECC Root",
+	"intermediate_common_name": "Caddy Local Authority - ECC Intermediate",
+	"root_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... gRw==\n-----END CERTIFICATE-----\n",
+	"intermediate_certificate": "-----BEGIN CERTIFICATE-----\nMIIB ... FzQ==\n-----END CERTIFICATE-----\n"
 }
diff --git a/src/docs/markdown/automatic-https.md b/src/docs/markdown/automatic-https.md index 9be4928..21c62de 100644 --- a/src/docs/markdown/automatic-https.md +++ b/src/docs/markdown/automatic-https.md @@ -179,7 +179,7 @@ The DNS challenge performs an authoritative DNS lookup for the candidate hostnam This challenge does not require any open ports, and the server requesting a certificate does not need to be externally accessible. However, the DNS challenge requires configuration. Caddy needs to know the credentials to access your domain's DNS provider so it can set (and clear) the special TXT records. If the DNS challenge is enabled, other challenges are disabled by default. -Since ACME CAs follow DNS standard when looking up TXT records for challenge verification, you can use CNAME records to delegate answering the challenge to other DNS zones. This can be used to delegate the `_acme-challenge` subdomain to another zone. This is particularly useful if your DNS provider doesn't provide an API, or isn't supported by one of the DNS plugins for Caddy. +Since ACME CAs follow DNS standards when looking up TXT records for challenge verification, you can use CNAME records to delegate answering the challenge to other DNS zones. This can be used to delegate the `_acme-challenge` subdomain to another zone. This is particularly useful if your DNS provider doesn't provide an API, or isn't supported by one of the DNS plugins for Caddy. DNS provider support is a community effort. [Learn how to enable the DNS challenge for your provider at our wiki.](https://caddy.community/t/how-to-use-dns-provider-modules-in-caddy-2/8148)