Add cname flattening announcement#2785
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughAdds a new Markdoc blog post at src/routes/blog/post/announcing-cname-flattening/+page.markdoc with front matter (layout, title, description, date, cover, timeToRead, author, category, featured) and content announcing CNAME flattening support for Appwrite Sites, including explanation, step-by-step usage (CNAME/ALIAS/ANAME records without changing nameservers) and resources. Adds a changelog entry at src/routes/changelog/(entries)/2026-03-05.markdoc referencing the announcement. Updates .optimize-cache.json to include the cover image images/blog/announcing-cname-flattening/cover.png with its hash. Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs). Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
src/routes/blog/post/announcing-cname-flattening/+page.markdoc (1)
31-35: Consider adding a CAA caveat for restrictive DNS setups.The steps are solid, but a brief note about CAA can prevent certificate issuance confusion for teams that enforce CAA records.
Suggested addition
4. Go to your DNS provider and create the required record. Use a CNAME for subdomains, or an ALIAS/ANAME record for the root domain. + - If your domain uses CAA records, make sure certificate issuance for Appwrite Cloud is allowed. 5. Return to Appwrite and verify the domain.Based on learnings: Appwrite Cloud Sites uses Certainly (Fastly's CA) for TLS certificates, and
0 issue "certainly.com"is the correct CAA value for Sites with CNAME flattening.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc around lines 31 - 35, Add a brief CAA caveat right after the DNS record instruction (after step 4) warning that restrictive CAA records can block certificate issuance and show the recommended CAA entry for Appwrite Cloud Sites: 0 issue "certainly.com"; instruct users to ensure any existing CAA records permit this CA or to add the above record so TLS issuance succeeds with CNAME flattening.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc:
- Line 19: The sentence "With CNAME flattening support, connecting a custom
domain is just a DNS record away..." implies instant activation; update that
line to clarify that after adding a CNAME/ALIAS/ANAME and verifying the domain
in the Console, DNS propagation and SSL certificate issuance can take some time
before the site is fully live. Locate the exact sentence in the post content and
replace or append a short note mentioning DNS propagation and certificate
issuance delays (e.g., "DNS propagation and SSL certificate issuance may take
some time before the site is fully live") so readers don't expect immediate
activation.
---
Nitpick comments:
In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc:
- Around line 31-35: Add a brief CAA caveat right after the DNS record
instruction (after step 4) warning that restrictive CAA records can block
certificate issuance and show the recommended CAA entry for Appwrite Cloud
Sites: 0 issue "certainly.com"; instruct users to ensure any existing CAA
records permit this CA or to add the above record so TLS issuance succeeds with
CNAME flattening.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 04be9278-0870-4f63-9203-d64e565e470e
📒 Files selected for processing (1)
src/routes/blog/post/announcing-cname-flattening/+page.markdoc
| 1. Open your site settings in the Appwrite Console. | ||
| 2. Add your custom domain. | ||
| 3. Appwrite provides a DNS target. | ||
| 4. Go to your DNS provider and create the required record. Use a CNAME for subdomains, or an ALIAS/ANAME record for the root domain. |
There was a problem hiding this comment.
In Cloudflare, this is achieved through a CNAME record for the root domain too
Besides, CNAME flattening is only relevant to root domains, so we don't need to talk about subdomains here tbh
Co-authored-by: Matej Bačo <matejbaco2000@gmail.com>
There was a problem hiding this comment.
Actionable comments posted: 1
♻️ Duplicate comments (1)
src/routes/blog/post/announcing-cname-flattening/+page.markdoc (1)
31-34:⚠️ Potential issue | 🟡 MinorUse provider-neutral wording in Step 3.
Line 33 is ungrammatical and narrower than the next step. Since the flow may end up using ALIAS/ANAME at the apex, “DNS record details” reads better here.
✏️ Suggested wording
-3. Appwrite provides a CNAME record details. +3. Appwrite provides the DNS record details.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc around lines 31 - 34, Replace the ungrammatical and provider-specific Step 3 text ("Appwrite provides a CNAME record details.") with a provider-neutral, grammatically correct phrase like "Appwrite provides the DNS record details." so it aligns with Step 4's mention of ALIAS/ANAME and apex/root handling; update the sentence in the +page.markdoc content for Step 3 (the line containing "Appwrite provides a CNAME record details.") to use "DNS record details" and correct article/grammar.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc:
- Around line 1-10: This post is missing required frontmatter keys "draft" and
"lastUpdated" which src/routes/blog/content.ts expects; open the +page.markdoc
for this post and add a draft field (e.g., draft: false) and a lastUpdated field
with an ISO date string (e.g., lastUpdated: 2026-03-06 or the same value as
date) in the YAML frontmatter so the blog index metadata is populated correctly.
---
Duplicate comments:
In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc:
- Around line 31-34: Replace the ungrammatical and provider-specific Step 3 text
("Appwrite provides a CNAME record details.") with a provider-neutral,
grammatically correct phrase like "Appwrite provides the DNS record details." so
it aligns with Step 4's mention of ALIAS/ANAME and apex/root handling; update
the sentence in the +page.markdoc content for Step 3 (the line containing
"Appwrite provides a CNAME record details.") to use "DNS record details" and
correct article/grammar.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 102564d1-d126-4859-acf9-e231ae857b23
📒 Files selected for processing (2)
src/routes/blog/post/announcing-cname-flattening/+page.markdocsrc/routes/changelog/(entries)/2026-03-05.markdoc
🚧 Files skipped from review as they are similar to previous changes (1)
- src/routes/changelog/(entries)/2026-03-05.markdoc
| --- | ||
| layout: post | ||
| title: "Announcing CNAME flattening support: Connect your domain without changing nameservers" | ||
| description: Appwrite Sites now supports CNAME flattening, so you can connect custom domains by adding a DNS record with your existing provider instead of migrating nameservers. | ||
| date: 2026-03-06 | ||
| cover: /images/blog/announcing-cname-flattening/cover.png | ||
| timeToRead: 4 | ||
| author: matej-baco | ||
| category: announcement | ||
| featured: false |
There was a problem hiding this comment.
Add the required draft and lastUpdated frontmatter.
src/routes/blog/content.ts treats both fields as required and reads them for every post. Leaving them out here will produce incomplete post metadata (draft: undefined, lastUpdated: Invalid Date) in the generated blog index.
🛠️ Minimal fix
---
layout: post
+draft: false
title: "Announcing CNAME flattening support: Connect your domain without changing nameservers"
description: Appwrite Sites now supports CNAME flattening, so you can connect custom domains by adding a DNS record with your existing provider instead of migrating nameservers.
date: 2026-03-06
+lastUpdated: 2026-03-06
cover: /images/blog/announcing-cname-flattening/cover.png
timeToRead: 4
author: matej-baco📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| --- | |
| layout: post | |
| title: "Announcing CNAME flattening support: Connect your domain without changing nameservers" | |
| description: Appwrite Sites now supports CNAME flattening, so you can connect custom domains by adding a DNS record with your existing provider instead of migrating nameservers. | |
| date: 2026-03-06 | |
| cover: /images/blog/announcing-cname-flattening/cover.png | |
| timeToRead: 4 | |
| author: matej-baco | |
| category: announcement | |
| featured: false | |
| --- | |
| layout: post | |
| draft: false | |
| title: "Announcing CNAME flattening support: Connect your domain without changing nameservers" | |
| description: Appwrite Sites now supports CNAME flattening, so you can connect custom domains by adding a DNS record with your existing provider instead of migrating nameservers. | |
| date: 2026-03-06 | |
| lastUpdated: 2026-03-06 | |
| cover: /images/blog/announcing-cname-flattening/cover.png | |
| timeToRead: 4 | |
| author: matej-baco | |
| category: announcement | |
| featured: false |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/routes/blog/post/announcing-cname-flattening/`+page.markdoc around lines
1 - 10, This post is missing required frontmatter keys "draft" and "lastUpdated"
which src/routes/blog/content.ts expects; open the +page.markdoc for this post
and add a draft field (e.g., draft: false) and a lastUpdated field with an ISO
date string (e.g., lastUpdated: 2026-03-06 or the same value as date) in the
YAML frontmatter so the blog index metadata is populated correctly.
3 participants
Summary by CodeRabbit