From f7fe5910322e78e31fe6018f47096da38c576e58 Mon Sep 17 00:00:00 2001 From: Matt Holt Date: Tue, 16 Jul 2019 14:04:26 -0600 Subject: [PATCH] Updated v2: Documentation (markdown) --- v2:-Documentation.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/v2:-Documentation.md b/v2:-Documentation.md index b15aa3c..6c5a0d7 100644 --- a/v2:-Documentation.md +++ b/v2:-Documentation.md @@ -84,9 +84,7 @@ $ caddy start [--config ] ``` -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 ] ``` -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": [] } ```