Skip to content

Point site at custom domain nto-registry.org - #1

Merged
gavinf97 merged 1 commit into
mainfrom
custom-domain-nto-registry-org
Jul 27, 2026
Merged

Point site at custom domain nto-registry.org#1
gavinf97 merged 1 commit into
mainfrom
custom-domain-nto-registry-org

Conversation

@gavinf97

Copy link
Copy Markdown
Member

Summary

  • Set Astro site/base for the apex domain nto-registry.org (was the biocomputingup.github.io/nto-registry/ project-site path).
  • Add site/public/CNAME so the custom domain survives every Actions-based Pages deploy (this deploy pipeline doesn't auto-generate a CNAME file the way branch-based Pages does).

Do not merge yet

Merging redeploys the site under the new domain, so hold off until:

  1. DNS is set at the registrar (arba.it panel) for nto-registry.org:
    A     @    185.199.108.153
    A     @    185.199.109.153
    A     @    185.199.110.153
    A     @    185.199.111.153
    
    optional IPv6:
    AAAA  @    2606:50c0:8000::153
    AAAA  @    2606:50c0:8001::153
    AAAA  @    2606:50c0:8002::153
    AAAA  @    2606:50c0:8003::153
    
    optional, if www.nto-registry.org should redirect to the apex:
    CNAME  www   biocomputingup.github.io.
    
  2. DNS has propagated (dig nto-registry.org +short returns the A records above).

After merge

In repo Settings → Pages, set Custom domain to nto-registry.org, wait for the green check, then enable Enforce HTTPS.

Test plan

  • dig nto-registry.org +short resolves to the GitHub Pages IPs
  • Settings → Pages custom domain check passes
  • https://nto-registry.org/ loads with working nav/links
  • Old URL https://biocomputingup.github.io/nto-registry/ redirects to the new domain

Set Astro `site`/`base` for the apex domain and add public/CNAME so
GitHub Pages (Actions-based deploy) keeps serving the custom domain
across rebuilds. Requires DNS (A/AAAA records at the registrar) and
the custom domain field in repo Settings > Pages to be set before
this takes effect.
@gavinf97
gavinf97 merged commit 500e759 into main Jul 27, 2026
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.

1 participant