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

Updated v2: Documentation (markdown)

Matt Holt 2019-07-16 14:04:26 -06:00
parent fc344742c7
commit f7fe591032
1 changed files with 4 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
v2:-Documentation.md

@ -84,9 +84,7 @@ $ caddy start
[--config <path>]
```
Starts the Caddy process, optionally bootstrapped with an
initial config file. Blocks until server is successfully
running (or fails to run), then returns.
Starts the Caddy process, optionally bootstrapped with an initial config file. Blocks until server is successfully running (or fails to run), then returns. On Windows, the child process will remain attached to the terminal, so closing the window will forcefully stop Caddy.
## run
@ -95,7 +93,7 @@ $ caddy run
[--config <path>]
```
Same as `start`, but blocks indefinitely. On windows it is better to use `run` rather than `start` as it makes more sense for the server to block the console window that is its parent.
Same as `start`, but blocks indefinitely; i.e. runs Caddy in "daemon" mode. On Windows, this is recommended over `caddy start` when running Caddy manually since it will be more obvious that Caddy is still running and bound to the terminal window.
## stop
@ -103,7 +101,7 @@ Same as `start`, but blocks indefinitely. On windows it is better to use `run` r
$ caddy stop
```
Stops the running Caddy process. (Note: this will stop any process named the same as the executable file.)
Gracefully the running Caddy process. (Note: this will stop any process named the same as the executable file.) On Windows, this stop is forceful and Caddy will not have an opportunity to do a graceful shutdown and clean up any active locks.
## reload
@ -694,7 +692,7 @@ Matches requests based on files on disk.
"file": {
"root": "",
"try_files": [],
"try_policy": ""
"try_policy": []
}
```