Repository navigation
chore(domain): the apex, ready to switch on - #14
Conversation
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.
Correction to the plan in the descriptionThis site publishes through a workflow, not from a branch ( So this PR on its own would have merged and changed nothing — the apex would have stayed unserved while the landing page carried #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 |
Refs #5
Do not merge this until DNS points at Pages. A
CNAMEfile makes GitHub redirectkaffeelisten.github.ioto 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.decanonicalandog:urlon the landing page,og:image, andcanonicalon the ImpressumNothing else refers to the hostname —
robots.txtis 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.
_github-pages-challenge-kaffeelistenTXT 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.wwwrecord currently points atcname.vercel-dns.com.CNAMEfile and starts serving the apex.kaffeelisten.defrom the Vercel project. Doing it earlier leaves the apex serving a 404 rather than the app; doing it later is harmless. The app keepskaffeelisten-kaffeelisten.vercel.appand is reachable throughout.What this does not do
The campus app loses its hostname and does not get a new one here:
itc1.kaffeelisten.dedoes 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.