Repository navigation
docs: clarify Cloudflare analytics rule precedence - #247
Merged
Merged
Conversation
officialsuyogdixit
enabled auto-merge (squash)
October 23, 2026 04:15
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.
Problem and change
The self-hosting guide still recommended disabling RUM to handle CSP conflicts. A matching Cloudflare Configuration Rule overrides Web Analytics settings and prevents automatic collection. Keep Rocket Loader off for the hostname, remove the conflicting RUM advice, and explain the existing beacon CSP and duplicate-injection boundary.
Update the readiness plan with completed PR #246 CI, deployment, live collection and processed hostname/country report evidence. The newly observed Feedbacks visits are explicitly QA traffic.
Verification
Scope: two canonical documentation files.
npm run check:harnesspasses, including documentation links and generated facts.npm run build:sitepasses for all 80 public HTML pages.npm run check:releasepasses.82126ec8c265fe2ed950612bfcf2bb7c63d09e72, and both published Markdown manuals match the built artifact byte for byte.Compatibility and operations
None. This PR changes two documentation files; no runtime, migration, dependency, CSP or deployment configuration changes.
npm run checkpasses in required CI.