chore(site): point Pages at www.ferrosa.ai - #30
Merged
Conversation
Switches the GitHub Pages custom domain from www.ferrosadb.com to www.ferrosa.ai. Merging this IS the cutover: GitHub reads docs/CNAME on main and reconfigures the custom domain from it. DNS is already staged — ferrosa.ai and www.ferrosa.ai resolve to the GitHub Pages IPs (185.199.108-111.153) DNS-only, so GitHub can validate the domain and issue the certificate. Expect a short window after merge: ferrosadb.com stops being a configured custom domain and will 404 until the Cloudflare redirect rule is enabled, and www.ferrosa.ai will not serve until GitHub issues its certificate. The site is also the software distribution endpoint (/LATEST, /install.sh), so that window affects installers and update checks — clients fetch with curl -fsSL and will follow the 301 once the redirect is live.
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
1 participant
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.
Merging this is the cutover. GitHub reads
docs/CNAMEonmainand reconfigures the Pages custom domain from it.Pre-flight (verified just now)
ferrosa.ai→ 185.199.108-111.153www.ferrosa.ai→ferrosadb.github.iowww.ferrosadb.com/LATESTv0.20.0(still live)Grey cloud matters: GitHub validates the custom domain by seeing DNS point at it, so proxying would block certificate issuance (and caused the earlier 525).
What happens on merge
www.ferrosa.ai.ferrosadb.comstops being a configured custom domain → GitHub 404s it.www.ferrosa.ai(usually minutes).The window between 2 and 3 is the outage. This site is also the software
distribution endpoint —
/LATEST(24 refs) and/install.sh(33 refs) arecompiled into installed clients — so update checks and installs fail during it.
Clients fetch with
curl -fsSL, so they follow the 301 once the Cloudflareredirect is enabled.
After merge
https://www.ferrosa.ai/LATESTto returnv0.20.0, and tickEnforce HTTPS in Settings → Pages.
be back to proxied/orange for the rule to run).
curl -sI https://ferrosadb.com/LATESTshowslocation: https://www.ferrosa.ai/LATEST— path preservation is the wholepoint; GoDaddy forwarding was ruled out because it 404s paths.
Rollback
Revert this commit and push. The cert for
www.ferrosadb.comis alreadyissued, so the old domain comes back quickly.
Still outstanding and unrelated to this PR: the root SPF on both domains still
includes
dc-aa8e722993._spfm.<domain>, which no longer resolves.