Updated v2: Documentation (markdown)

Matt Holt 2019-07-05 15:32:28 -06:00
parent 35c57bf98b
commit 3a83d97b99

@ -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: Each Caddy module has a name, scope/namespace, and ID:
- A name looks like `a.b.c.module_id` - A name looks like `a.b.c.module_id`
- The namespace would be `a.b.c`. - The namespace would be `a.b.c`
- The module ID is `module_id` which must be unique in its namespace. - 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. 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 ## storage
@ -1219,6 +1219,7 @@ A distributed STEK provider module. This allows Caddy to share STEKs among other
```json ```json
{ {
"provider": "distributed",
"storage": {} "storage": {}
} }
``` ```