mirrors/caddy-website
1
0
Fork 0
mirror of https://github.com/caddyserver/website.git synced 2025-04-23 05:26:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: Updates for Caddy v2.4.4 (#189)

Browse source 
* docs: Updates for Caddy v2.4.4

* Adjust wording

* Clarify HTTPS proxy usage, reorder lb policies for clarity

* Reorder directives, add comments
This commit is contained in:
Francis Lavoie 2021-08-31 13:39:15 -04:00 • committed by GitHub
parent 83fdd80db1
commit 3dac36ebc8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
10 changed files with 119 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

19
src/docs/markdown/v2-upgrade.md
View file

@ -241,24 +241,9 @@ The recommended way to enable access logging is simply:
log
```
which emits structured logs to stderr. (You can also emit to a file or network socket; see docs.)
which emits structured logs to stderr. (You can also emit to a file or network socket; see the [`log`](/docs/caddyfile/directives/log) directive docs.)
Although we recommend everyone use [structured logging](/docs/logging), you can still write Common Log Format (CLF) to a file, if you must:
- **v1:**
```
log access.log
```
- **v2:**
```caddy-d
log {
output file access.log
format single_field common_log
}
```
But we recommend this only for transitioning while your legacy systems still require CLF.
By default, logs will be in [structured](/docs/logging) JSON format. If you still need logs in Common Log Format (CLF) for legacy reasons, you may use the [`format-encoder`](https://github.com/caddyserver/format-encoder) plugin.
### proxy