Cutlery/caddy
1
0
Fork 0
mirror of https://github.com/caddyserver/caddy.git synced 2025-08-11 09:16:26 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated v2: Config from Scratch (markdown)

Matt Holt 2019-07-03 13:26:58 -06:00
parent 8f4d2389ae
commit 21497d9397
1 changed files with 49 additions and 55 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
v2:-Config-from-Scratch.md

@ -1,11 +1,10 @@
Empty config (does nothing): An empty config does nothing:
```json ```json
{} {}
``` ```
This is an empty HTTP server, which responds on port 80 to any host, but with an empty response:
Empty HTTP server (responds with empty responses):
```json ```json
{ {
@ -21,7 +20,7 @@ Empty HTTP server (responds with empty responses):
} }
``` ```
Static file server out of the specified directory: This is a static file server out of the the `/var/www` directory:
```json ```json
{ {
@ -45,7 +44,7 @@ Static file server out of the specified directory:
} }
``` ```
Same as above, but with automatic HTTPS (including HTTP->HTTPS redirects): And this is the same, but with automatic HTTPS (notice that we now serve on the HTTPS port; any port will do, as long as it's not the HTTP port):
```json ```json
{ {
@ -56,11 +55,7 @@ Same as above, but with automatic HTTPS (including HTTP->HTTPS redirects):
"listen": [":443"], "listen": [":443"],
"routes": [ "routes": [
{ {
"match": [ "match": [{"host": ["example.com"]}],
{
"host": ["example.com"]
}
],
"respond": { "respond": {
"responder": "file_server", "responder": "file_server",
"root": "/var/www" "root": "/var/www"
@ -72,7 +67,6 @@ Same as above, but with automatic HTTPS (including HTTP->HTTPS redirects):
} }
} }
} }
``` ```
The reason the above config uses HTTPS is because the host matcher informs Caddy which hostnames to manage certificates for. The reason this particular config gets automatic HTTPS is because the host matcher informs Caddy which hostnames to manage certificates for.