mirror of
https://github.com/caddyserver/website.git
synced 2025-04-21 20:46:15 -04:00
M1 -> Apple
As there is now an M2 chip announced
This commit is contained in:
parent
655786d85e
commit
52de5be0f8
2 changed files with 2 additions and 2 deletions
|
@ -151,7 +151,7 @@ A module's life begins when it is loaded by a host module. The following happens
|
||||||
5. At this point, the host module is given the loaded guest module as an `interface{}` value, so the host module will usually type-assert the guest module into a more useful type. Check the documentation for the host module to know what is required of a guest module in its namespace, e.g. what methods need to be implemented.
|
5. At this point, the host module is given the loaded guest module as an `interface{}` value, so the host module will usually type-assert the guest module into a more useful type. Check the documentation for the host module to know what is required of a guest module in its namespace, e.g. what methods need to be implemented.
|
||||||
6. When a module is no longer needed, and if it is a [caddy.CleanerUpper](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#CleanerUpper), the `Cleanup()` method is called.
|
6. When a module is no longer needed, and if it is a [caddy.CleanerUpper](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#CleanerUpper), the `Cleanup()` method is called.
|
||||||
|
|
||||||
Note that multiple loaded instances of your module may overlap at a given time! During config changes, new modules are started before the old ones are stopped. Be sure to use global state carefully. Use the [caddy.UsagePool](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#UsagePool) type to help manage global state across module loads.
|
Note that multiple loaded instances of your module may overlap at a given time! During config changes, new modules are started before the old ones are stopped. Be sure to use global state carefully. Use the [caddy.UsagePool](https://pkg.go.dev/github.com/caddyserver/caddy/v2?tab=doc#UsagePool) type to help manage global state across module loads. If your module listens on a socket, use `caddy.Listen*()` to get a socket that supports overlapping usage.
|
||||||
|
|
||||||
### Provisioning
|
### Provisioning
|
||||||
|
|
||||||
|
|
|
@ -42,7 +42,7 @@
|
||||||
<option value="linux-ppc64le">Linux ppc64le</option>
|
<option value="linux-ppc64le">Linux ppc64le</option>
|
||||||
<option value="linux-s390x">Linux s390x</option>
|
<option value="linux-s390x">Linux s390x</option>
|
||||||
<option value="darwin-amd64">macOS amd64 (Intel)</option>
|
<option value="darwin-amd64">macOS amd64 (Intel)</option>
|
||||||
<option value="darwin-arm64">macOS arm64 (M1)</option>
|
<option value="darwin-arm64">macOS arm64 (Apple)</option>
|
||||||
<option value="openbsd-amd64">OpenBSD amd64</option>
|
<option value="openbsd-amd64">OpenBSD amd64</option>
|
||||||
<option value="openbsd-arm-6">OpenBSD arm 6</option>
|
<option value="openbsd-arm-6">OpenBSD arm 6</option>
|
||||||
<option value="openbsd-arm-7">OpenBSD arm 7</option>
|
<option value="openbsd-arm-7">OpenBSD arm 7</option>
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue