Repository navigation
docs: complete the published PHP Server configuration and admission reference - #398
Merged
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Operators could not find35 declared Server controls or understand namespace HTTP/durable admission. All eight config references now cover the qualified published PHP2.11.0 contract’s164 variables with defaults, purposes and exact legacy aliases. All eight admission guides add counted/exempt route families, fixed-minute/burst behavior, shared-Redis scope, worked default/override/hard-cap examples, refusal/retry hints, durable resource counts and metrics. The selected tuple is unchanged. Refs #335.
The new build check reads a versioned published-contract snapshot with exact source/image provenance, checks every locale, and preserves editable prose. Five focused tests pass, including a name mentioned only in prose, a wrong alias, empty default/purpose and moving-source provenance. All seven source hashes and executable blocks match English; local translation and whitespace checks pass.
Installed qualification records cold configuration controls, actual HTTP rate/minute-reset/refusal/route exemption, service-held concurrency refusal/release and basic SQLite metadata-registration quotas. Two API replicas sharing Redis7.4.11 and an ephemeral SQLite database share one rate/concurrency budget. These controls do not qualify production SQL, HA, native Server or every workflow lifecycle. No source/vendor overlays or product changes were used.
A negative control found a separate published product defect: malformed namespace override JSON is silently dropped, falling back to global defaults even under strict env audit. The guide states this current limitation in all eight locales and narrows503 claims to validated numeric failures/unavailable coordination. It does not substitute documentation for that fix. The original root-holder fixture failure and corrected application-user comparison also remain recorded.
Current source
5cb43b744823bd4c4c0b38460194fb7f4fd8a600awaits exact-head CI/Sonar review, normal merge, actual Pages and all sixteen live guides. No new Server/runtime/image adoption or released validation safeguard is claimed.