diff options
| author |  Miek Gieben <miek@miek.nl>
| 2017-09-16 14:13:28 +0100 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2017-09-16 14:13:28 +0100 |
| commit | be4770927048627b59a6ce80587d668d7c028518 (patch) | |
| tree | 2a90130bb39467ff2ea879c8b4f204c39c64cf43 /plugin.md | |
| parent | 6f874f0bd12f70efb31c88945dd66293a781604e (diff) | |
| download | coredns-be4770927048627b59a6ce80587d668d7c028518.tar.gz coredns-be4770927048627b59a6ce80587d668d7c028518.tar.zst coredns-be4770927048627b59a6ce80587d668d7c028518.zip | |
More Middleware -> Plugin conversions (#1088)
Forgot about these.
Diffstat (limited to 'plugin.md')
| -rw-r--r-- | plugin.md | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -1,6 +1,6 @@ -# Middleware +# Plugins -## Writing Middleware +## Writing Plugins From the Caddy docs: @@ -136,7 +136,7 @@ compute.internal. 3600 IN MX 10 mx.compute.internal. ## Qualifying for main repo -Middleware for CoreDNS can live out-of-tree, `plugin.cfg` defaults to CoreDNS' repo but other +Plugins for CoreDNS can live out-of-tree, `plugin.cfg` defaults to CoreDNS' repo but other repos work just as well. So when do we consider the inclusion of a new plugin in the main repo? * First, the plugin should be useful for other people. "Useful" is a subjective term. We will |