Skip to content

chore(domain): the apex, ready to switch on - #14

Merged
arudaev merged 1 commit into
mainfrom
chore/apex-cutover
Nov 6, 2026
Merged

arudaev merged 1 commit into
mainfrom
chore/apex-cutover

Conversation

@arudaev

@arudaev arudaev commented Nov 6, 2026

Copy link
Copy Markdown
Member

Refs #5

Do not merge this until DNS points at Pages. A CNAME file makes GitHub redirect kaffeelisten.github.io to the custom domain, so merging while the apex still resolves to Vercel takes the working landing page offline instead of moving it. That is the whole reason this is a separate, unmerged PR rather than part of the last one.

What is in it

  • CNAME → kaffeelisten.de
  • The four absolute URLs that name the host: canonical and og:url on the landing page, og:image, and canonical on the Impressum

Nothing else refers to the hostname — robots.txt is relative and there is no sitemap.

The order to do it in

Steps 1–3 are Alexander's: DNS is external, at Hetzner, so neither GitHub nor Vercel can write it.

  1. A day ahead: lower the TTL on the apex records from 7200 to 300. The cutover then costs five minutes of staleness instead of two hours.
  2. Verify the domain for the organisation. GitHub → organisation Settings → Pages → Verified domains issues a _github-pages-challenge-kaffeelisten TXT record with a token. Add it exactly as shown. Without it the apex can be claimed by another account, and Pages will not serve it.
    Remember Hetzner appends the zone to the Name field: the record name is _github-pages-challenge-kaffeelisten, not the full hostname.
  3. Switch the records:
    @    A      185.199.108.153
    @    A      185.199.109.153
    @    A      185.199.110.153
    @    A      185.199.111.153
    www  CNAME  kaffeelisten.github.io.
    
    The www record currently points at cname.vercel-dns.com.
  4. Merge this PR. Pages picks up the CNAME file and starts serving the apex.
  5. Then, and only then, remove kaffeelisten.de from the Vercel project. Doing it earlier leaves the apex serving a 404 rather than the app; doing it later is harmless. The app keeps kaffeelisten-kaffeelisten.vercel.app and is reachable throughout.
  6. Enforce HTTPS in Pages settings once the certificate is issued, which takes a few minutes after step 4.

What this does not do

The campus app loses its hostname and does not get a new one here: itc1.kaffeelisten.de does not exist yet, and the app has no database behind it anyway while production is paused (kaffeelisten/playbook#9). Nothing regresses — the apex has not worked since before this was noticed.

CNAME plus the four absolute URLs that name the host: canonical and og:url
on the landing page, og:image, and canonical on the Impressum.

Do not merge before DNS points at Pages. A CNAME file makes GitHub redirect
kaffeelisten.github.io to the custom domain, so merging this while the apex
still resolves to Vercel takes the working landing page offline rather than
moving it.
@github-actions github-actions Bot added the area:landing The landing page label Nov 6, 2026
@github-actions github-actions Bot added the type:task Work with a clear finish line that is not a feature label Nov 6, 2026
@arudaev arudaev added the needs-decision Waiting on a founder decision label Nov 6, 2026
@arudaev

arudaev commented Nov 6, 2026

Copy link
Copy Markdown
Member Author

Correction to the plan in the description

This site publishes through a workflow, not from a branch (build_type: workflow, Source = GitHub Actions). On a workflow-published site a CNAME file in the repository root is not picked up: it has to be inside the uploaded artifact, and the workflow copies a fixed list of files that does not include it.

So this PR on its own would have merged and changed nothing — the apex would have stayed unserved while the landing page carried canonical pointing at a host that answers nothing.

#16 fixes the copy step (and, separately, publishes the Impressum, which has been a 404). Merge #16 first. After that this PR does what its description says.

Step 2 of the order is also softer than written: verifying the domain for the organisation is recommended, not required. A custom domain works without it. What it buys is protection against someone else claiming kaffeelisten.de on GitHub Pages if this repository is ever deleted or transferred. It lives in the organisation's settings, not this repository's.

@arudaev
arudaev merged commit c37237e into main Nov 6, 2026
8 checks passed
@arudaev
arudaev deleted the chore/apex-cutover branch November 6, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:landing The landing page needs-decision Waiting on a founder decision type:task Work with a clear finish line that is not a feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant