Document run --print-env

Matt Holt 2019-07-18 10:58:21 -06:00
parent b8f79ba9fa
commit 6d0d47f9d7

@ -91,9 +91,10 @@ Starts the Caddy process, optionally bootstrapped with an initial config file. B
``` ```
$ caddy run $ caddy run
[--config <path>] [--config <path>]
[--print-env]
``` ```
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. 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. If `--print-env` is specified, the environment as seen by the Caddy process will be printed before starting. This is the same as the `environ` command but does not quit after printing.
## stop ## stop
@ -101,7 +102,7 @@ Same as `start`, but blocks indefinitely; i.e. runs Caddy in "daemon" mode. On W
$ caddy stop $ caddy stop
``` ```
Gracefully stops 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. A graceful shutdown can be performed by POSTing to `/stop` Admin endpoint [soon to be implemented](https://github.com/caddyserver/caddy/pull/2671). Gracefully stops 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. A graceful shutdown can be performed by POSTing to /stop endpoint [soon to be implemented](https://github.com/caddyserver/caddy/pull/2671).
## reload ## reload