Skip to content

Clarify Cloudflare proxy requirement in CNAME flattening blog#2902

Merged
eldadfux merged 3 commits intomainfrom
clarify-cname-flattening-proxy-note
Apr 19, 2026
Merged

Clarify Cloudflare proxy requirement in CNAME flattening blog#2902
eldadfux merged 3 commits intomainfrom
clarify-cname-flattening-proxy-note

Conversation

@ChiragAgg5k
Copy link
Copy Markdown
Member

Summary

  • Reframes the Cloudflare mention so it no longer implies users keep full Cloudflare HTTP-layer features (caching, security headers) alongside Appwrite. Appwrite serves sites through its own CDN, so the proxy must be off.
  • Adds a clear note in both the "Add a record, not a migration" section and step 4 of "Connect your domain" that Cloudflare records must be set to DNS only (grey cloud), not proxied.
  • DNS-layer protections and MX records stay with the existing provider; Appwrite handles CDN / SSL / edge security.

Test plan

  • Preview renders correctly at /blog/post/announcing-cname-flattening
  • Confirm copy reads naturally and doesn't contradict other blog sections

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-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Apr 19, 2026

Greptile Summary

This 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/5

Safe 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

Filename Overview
src/routes/blog/post/announcing-cname-flattening/+page.markdoc Three targeted copy edits: intro reworded to remove misleading "caching/security" references; "Add a record" section clarified to distinguish DNS-layer vs. CDN features and adds Cloudflare grey-cloud note; step 4 adds the same grey-cloud instruction inline.

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.
@eldadfux eldadfux merged commit 6bb4728 into main Apr 19, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants