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

docs: Minor tweaks, clarifications.

Browse source
This commit is contained in:
Matthew Holt 2020-04-01 11:09:26 -06:00
parent 3ecf039665
commit 836e15afbc
No known key found for this signature in database
GPG key ID: 2A349DD577D586A5
4 changed files with 8 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
src/docs/markdown/architecture.md
View file

@ -135,7 +135,7 @@ You can [watch a video about the design of Caddy 2 here](https://www.youtube.com
A config reload works by provisioning the new modules, and if all succeed, the old ones are cleaned up. For a brief period, two configs are operational at the same time.
Each configuration is associated with a [context](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#Context) which holds all the module state, so most state escapes the scope of a config. This is good news for correctness, performance, and simplicity!
Each configuration is associated with a [context](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#Context) which holds all the module state, so most state never escapes the scope of a config. This is good news for correctness, performance, and simplicity!
However, sometimes truly global state is necessary. For example, the reverse proxy may keep track of the health of its upstreams; since there is only one of each upstream globally, it would be bad if it forgot about them every time a minor config change was made. Fortunately, Caddy [provides facilities](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#UsagePool) similar to a language runtime's garbage collector to keep global state tidy.