Clarify Cloudflare proxy requirement in CNAME flattening blog#2902
Clarify Cloudflare proxy requirement in CNAME flattening blog#2902
Conversation
Appwrite serves sites through its own CDN, so the Cloudflare (or similar) proxy must be disabled for CNAME flattening to work. The post previously implied users could keep full Cloudflare behavior, which misled readers about HTTP-layer features.
Greptile SummaryThis PR corrects three passages in the CNAME flattening blog post that implied Cloudflare's HTTP-layer features (caching, security headers) remain active when using CNAME flattening with Appwrite. The intro now lists only what genuinely stays with the existing provider (email routing, DNS-layer protections), step 4 and the "Add a record" section both include a clear DNS only (grey cloud) callout for Cloudflare users, and Appwrite's own CDN/SSL/edge-security role is made explicit. The previous outside-diff concern about the intro implying Cloudflare proxy features could be preserved is resolved by the new wording on line 13. Confidence Score: 5/5Safe to merge — all changes are accurate content clarifications with no remaining blocking issues. The prior P2 concern about the intro was resolved by the new wording. All three edits are factually correct and consistent with each other. No code logic or data is affected. No files require special attention. Important Files Changed
Reviews (3): Last reviewed commit: "Replace em dash with period in Connect y..." | Re-trigger Greptile |
Dropped caching and security from the "giving up" list — those are HTTP-layer features that Appwrite's CDN handles, not things CNAME flattening hands back to the provider. Keeps the intro consistent with the corrected messaging later in the post.
Summary
Test plan
/blog/post/announcing-cname-flattening