I followed these instructions on a fresh Debian 12 box, seemingly
successfully. But `systemctl reload caddy` would reject my Caddyfile
that tried to use those custom modules, logging "unknown module" errors,
even though `caddy list-modules` reported that they were installed.
After reading [a comment on `caddyserver/cache-handler`][c], I tried
running `systemctl restart caddy`, which immediately fixed the issue.
In retrospect, it makes sense that since `apt install caddy` starts the
systemd service, replacing the binary on the filesystem does nothing to
change the running server. But the instructions didn't suggest this, and
I'm used to only `reload`ing Caddy, so I didn't think of it myself.
[c]: https://github.com/caddyserver/cache-handler/issues/33#issuecomment-1234457086
wchargin-branch: custom-build-systemctl-restart
wchargin-source: 91f0cc15ae1eb8143fccc271e7aa2ecae5bc3da8
* docs: Changes for v2.5.2 release
* docs: Remove -X POST
Curl automatically uses POST for -d and --data-binary.
I intentionally left it in to be explicit to learners, but
maybe best practices are better.
* api: /adapt endpoint and Etag usage
* api: Minor tweaks
* Alright fine
* Clarify Etag usage
* CEL embedded matchers
* Oops
* Lots more adjustments
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
* add custom binary support files docs
rephrase
* Update src/docs/markdown/build.md
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
* add link to build on package docs
Co-authored-by: Francis Lavoie <lavofr@gmail.com>
* docs: Some cleanup, some v2.4.0 additions
- Add `abort` directive docs
- Add a note in `handle` to cross-link to `handle_path`
- Add another example in `handle_errors` that shows how an `expression` matcher can be used to pair with it
- Add a cat emoji to handle_errors because 😸
- Add `file_server` to one of the `php_fastcgi` examples, it's rare that you'll ever use it without `file_server` so might as well include it there
- Add a TOC to `reverse_proxy` cause it's such a long page. Maybe we'll add one to other pages as well, but TBD
- Clarify the upstream address stuff a bit after some discussion in https://caddy.community/t/reverse-proxy-with-multiple-different-upstreams-with-paths/11512/12 and mention `rewrite` as the alternative
- Use the `{re.*.*}` shortcut in the Caddyfile matcher docs, links to the placeholder mapping to let people trace where that comes from
* docs: Revise the `handle` cross-linking, add another example
* docs: Bump minimum Go version to 1.15
* 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
* docs: Review feedback
* docs: Link to https://golang.org/doc/install, better instructions
We now have only 1 download page, yay. Install docs are organized better. Less confusing.
Automatic HTTPS docs improved, and menu added.
Other minor updates to bring up to speed for v2.3.
