Repository navigation
chore(dns): drop the zone file from the site repository - #1
Merged
Merged
Conversation
The zone was a snapshot of records that live in Cloudflare, and Cloudflare is where they are actually edited. A copy here has no mechanism keeping it in step: nothing imports it, nothing validates it, and nothing fails when the two diverge — so its only guaranteed property over time is being wrong in a way that looks authoritative. It also sat in the wrong repository. This one builds a static site; DNS for the apex is infrastructure the site has no relationship with beyond being served at the end of it. The content is not lost — it remains in history at 052224c, which is the right place for a record of what was configured and when. Signed-off-by: Wessel Verheij <info@nightworks.io>
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.
Removes
dns/beatrax.app.zone.The zone was a snapshot of records that live in Cloudflare, and Cloudflare is where they are actually edited. Nothing here imports it, validates it, or fails when the two diverge — so the only property the copy is guaranteed to acquire over time is being wrong while looking authoritative. A DNS record that is nearly right is worse than no record at all.
It also sat in the wrong repository. This one builds a static site; DNS for the apex is infrastructure the site has no relationship with beyond being served at the end of it.
Nothing references the folder — checked across Markdown, workflows,
.astroand.ts. The content stays in history at052224c, which is the right place for a record of what was configured and when.If a checked-in zone is still wanted, it belongs somewhere it can be enforced — a Terraform or OctoDNS definition that Cloudflare is applied from, rather than a transcript of what was clicked.