ReleaseRestGateway
Corex\Config\Releases\ReleaseRestGateway · class · Config layer
Who may use the Releases routes, and the shape every one of them answers in (spec 107, plan D12 and D13). Every answer carries the installer’s mark. A shared host puts pages of its own in front of a site (a challenge, a “too many requests”, a maintenance page), and they arrive with status 200 and a body that is not this. The screen takes an answer as one only if it is marked, and anything else as “wait and ask again”: so the mark is on refusals too, which are answers.
Public API
Section titled “Public API”__construct(ReleaseCaller $caller)
Section titled “__construct(ReleaseCaller $caller)”mayManage(): bool
Section titled “mayManage(): bool”Installing a release is its own ability. On a network it is the network’s to do, from the main site: a release replaces code every site runs.
answer(WP_REST_Request $request, callable $answer): WP_REST_Response
Section titled “answer(WP_REST_Request $request, callable $answer): WP_REST_Response”Run one of the routes and answer for it.