mirror of
https://github.com/caddyserver/website.git
synced 2025-05-06 11:47:12 -04:00
docs: A bunch more additions since v2.3.0
I went through the whole list of commits here: https://github.com/caddyserver/caddy/compare/v2.3.0...ec3ac84
This commit is contained in:
parent
06411b1f3f
commit
0a07434a42
4 changed files with 37 additions and 3 deletions
|
@ -222,7 +222,8 @@ NOTE: Due to [a bug in Go](https://github.com/golang/go/issues/29228), version i
|
|||
<pre><code class="cmd bash">caddy reload
|
||||
[--config <path>]
|
||||
[--adapter <name>]
|
||||
[--address <interface>]</code></pre>
|
||||
[--address <interface>]
|
||||
[--force]</code></pre>
|
||||
|
||||
Gives the running Caddy instance a new configuration. This has the same effect as POSTing a document to the [/load endpoint](/docs/api#post-load), but this command is convenient for simple workflows revolving around config files. Compared to the `stop`, `start`, and `run` commands, this single command is the correct, semantic way to change/reload the running configuration.
|
||||
|
||||
|
@ -234,6 +235,8 @@ Because this command uses the API, the admin endpoint must not be disabled.
|
|||
|
||||
`--address` needs to be used if the admin endpoint is not listening on the default address and if it is different from the address in the provided config file. Note that only TCP addresses are supported at this time.
|
||||
|
||||
`--force` will cause a reload to happen even if the specified config is the same as the one the running Caddy instance is already using. Can be useful to force Caddy to reload TLS certificate files specified to load in the config, if they've become stale.
|
||||
|
||||
|
||||
|
||||
### `caddy reverse-proxy`
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue