From 2fd7bef5204f05a2275d2ba2d6e43476e4fa333d Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Mon, 18 Jul 2016 17:03:37 -0600 Subject: [PATCH] Updated Extending Caddy (markdown) --- Extending-Caddy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Extending-Caddy.md b/Extending-Caddy.md index 75b4eed..7d09430 100644 --- a/Extending-Caddy.md +++ b/Extending-Caddy.md @@ -6,9 +6,9 @@ Plugins are flexible ways to add missing functionality to Caddy. Plugins can: - Implement an entire server type (HTTP, for instance) - Customize how the Caddyfile is loaded -- Run functions when servers are started, restarted, or stopped (including background services or goroutines) +- Run functions when servers are started, restarted, or stopped (including background services / goroutines) - Define new directives for the Caddyfile -- Wire up ACME DNS challenge solvers for the various DNS providers +- Wire up ACME DNS challenge solvers for your favorite DNS providers Notice that Caddy's HTTP server is a _plugin_. Caddy's advanced TLS features are _plugins_. The different ways Caddy loads the Caddyfile are all _plugins_. And every single directive you type into the Caddyfile is a _plugin_. @@ -61,4 +61,4 @@ Learn how to write a specific kind of Caddy plugin. ## Adding Your Plugin to the Caddy Web Site -(TODO) \ No newline at end of file +[Follow these instructions](https://github.com/mholt/caddy/wiki/Publishing-a-Plugin-to-the-Download-Page) to add your plugin to the Caddy download page. \ No newline at end of file