From 3a83d97b9929097d1c1b48b23cbe851707bd53fa Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Fri, 5 Jul 2019 15:32:28 -0600 Subject: [PATCH] Updated v2: Documentation (markdown) --- v2:-Documentation.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/v2:-Documentation.md b/v2:-Documentation.md index dfe0302..a2cf974 100644 --- a/v2:-Documentation.md +++ b/v2:-Documentation.md @@ -246,8 +246,8 @@ Caddy modules are the evolution of "plugins" in Caddy 1, and although modules ar Each Caddy module has a name, scope/namespace, and ID: - A name looks like `a.b.c.module_id` -- The namespace would be `a.b.c`. -- The module ID is `module_id` which must be unique in its namespace. +- The namespace would be `a.b.c` +- The module ID is `module_id` which must be unique in its namespace When the context makes it obvious what the namespace is, we generally refer to the module ID as the name, or use the terms interchangably; and in conversation the namespace can be omitted. @@ -323,7 +323,7 @@ Configures the administration endpoint. } ``` -- `listen`: the address to which the admin endpoint's listener should bind itself. +- `listen`: the address to which the admin endpoint's listener should bind itself. At least one listener is required. ## storage @@ -1219,6 +1219,7 @@ A distributed STEK provider module. This allows Caddy to share STEKs among other ```json { + "provider": "distributed", "storage": {} } ```