From cce02cd922a5a44089091227a1f86556ada03454 Mon Sep 17 00:00:00 2001 From: Francis Lavoie Date: Mon, 6 Nov 2023 04:27:36 -0500 Subject: [PATCH] Minor profiling page adjustments --- src/docs/markdown/getting-started.md | 8 ++++---- src/docs/markdown/profiling.md | 26 ++++++++++++++++++++++---- 2 files changed, 26 insertions(+), 8 deletions(-) diff --git a/src/docs/markdown/getting-started.md b/src/docs/markdown/getting-started.md index 60a2bbf..f9b81a9 100644 --- a/src/docs/markdown/getting-started.md +++ b/src/docs/markdown/getting-started.md @@ -132,7 +132,7 @@ Save that to a file named `Caddyfile` (no extension) in the current directory. -Stop Caddy if it is already running (Ctrl+C), then run: +Stop Caddy if it is already running (Ctrl+C), then run: 
caddy adapt
@@ -233,7 +233,7 @@ As you can see, Caddy is well-suited for a wide variety of use cases and deploym ## Start, stop, run -Since Caddy is a server, it runs indefinitely. That means your terminal won't unblock after you execute `caddy run` until the process is terminated (usually with Ctrl+C). +Since Caddy is a server, it runs indefinitely. That means your terminal won't unblock after you execute `caddy run` until the process is terminated (usually with Ctrl+C). Although `caddy run` is the most common and is usually recommended (especially when making a system service!), you can alternatively use `caddy start` to start Caddy and have it run in the background: @@ -241,7 +241,7 @@ Although `caddy run` is the most common and is usually recommended (especially w This will let you use your terminal again, which is convenient in some interactive headless environments. -You will then have to stop the process yourself, since Ctrl+C won't stop it for you: +You will then have to stop the process yourself, since Ctrl+C won't stop it for you: 
caddy stop
@@ -256,7 +256,7 @@ Your server can perform zero-downtime config reloads/changes. All [API endpoints](/docs/api) that load or change config are graceful with zero downtime. -When using the command line, however, it may be tempting to use Ctrl+C to stop your server and then restart it again to pick up the new configuration. Don't do this: stopping and starting the server is orthogonal to config changes, and will result in downtime. +When using the command line, however, it may be tempting to use Ctrl+C to stop your server and then restart it again to pick up the new configuration. Don't do this: stopping and starting the server is orthogonal to config changes, and will result in downtime.