You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Serve devantler.tech and portal.devantler.tech from the platform #6177
The business-site portal will live at portal.devantler.tech (maintainer, 2026-11-13). The platform serves the app today only under the public staging name business-site.platform.devantler.tech (#6174). The gateway's certificate covers only platform.devantler.tech and *.platform.devantler.tech.
What
TLS: add a gateway listener and certificate for portal.devantler.tech, as ascoachingogvaner.dk has.
Route: change the business-site entry in restrict-tenant-route-hostnames from the staging name to portal.devantler.tech, with fixtures.
Listeners and certificates: add them for devantler.tech and www.devantler.tech beside portal.devantler.tech, all from the cluster issuer.
Route allow-list: admit those three names plus the staging name, which the WebApp keeps for pre-switch verification.
DNS: external-dns creates portal.devantler.tech immediately. The apex and www keep pointing at Pages until the cutover hands their records to external-dns, because external-dns never overwrites a record it does not own.
changed the title [-]Serve the business-site portal at portal.devantler.tech[/-][+]Serve devantler.tech and portal.devantler.tech from the platform[/+]on Nov 13, 2026
Blocker for the re-pin: v3.2.0 was signed by publish-app v21.3.1. The platform approves only 467f0758 and d8b5d0e9 for business-site, because Dependabot moved the caller off the approved revision. The canonical upgrade tooling also needs the v3.0.0 upgrade record settled first, and the daily regeneration that settles it has failed since 3 November for this reason and an identical aws drift (Restore complete publisher observations after AWS and Khoist caller transitions #5267).
devantler.tech cutover: plan and rollback (written before any change)
Parity (15 November)
A crawl compared all 305 public paths on live Pages with the platform runtime (devantler.tech pinned to the gateway): English and Danish pages, journal, tags, templates, assets, PDFs, RSS, sitemap, robots and historical redirects. 289 match byte for byte. Content types match (JS is text/javascript instead of application/javascript, which is equivalent). Certificate on the gateway is valid for devantler.tech, www and portal.
Expected:/portal… redirects to portal.devantler.tech, where the portal stays off (404). /healthz exists only on the platform. The Projects page shows a different "Ranking checked" date because Pages rebuilds daily. publication-source.json is the Pages publisher's own receipt; it goes with Pages.
DNS hand-over (declarative, in devantler-tech/cloudflare; cloudflare#21)
The zone snapshot shows the apex is one flattened CNAME to devantler.github.io (DNS-only), and www a proxied CNAME to the same target. That makes the switch two small changes, neither with a gap and neither changing external-dns's configuration (#6312, option 2):
B. www → external-dns. devantler-tech/cloudflare creates the marker _externaldns.cname-www.devantler.tech with content heritage=external-dns,external-dns/owner=platform.devantler.tech,external-dns/resource=httproute/business-site/business-site-public, and drops the www CNAME from its state (destroy=false). Within a minute external-dns deletes the CNAME and creates proxied gateway A/AAAA records in one Cloudflare batch, which is a single transaction.
C. Apex → www. After www is verified on the gateway, devantler-tech/cloudflare edits the apex CNAME in place to www.devantler.tech, proxied. A single record edit means no gap, and the apex then follows the gateway through www with no manual step.
The apex MX, SPF, Apple, DMARC, DKIM and Pages-challenge records stay as they are in OpenTofu. external-dns plans no apex change today, after B or after C (checked with external-dns v0.23.0's registry and planner on a zone of this shape), so devantler.tech stays in the HTTPRoute, where the gateway needs it.
During the switch, resolvers that cached the old answers (five-minute TTL) still reach Pages, which serves the same pages.
Verification (agent, right after)
Public DNS shows only Cloudflare addresses for both names. The crawl is re-run against live DNS: every path matches, certificates are valid, www and plain HTTP give 301, and portal.devantler.tech/portal/ is still 404.
Rollback (until Pages is retired)
Pages keeps its custom domain and certificate (valid to 2027-01-04) until verification passes.
Apex: edit the apex CNAME back to devantler.github.io with proxy off. One edit, no gap.
www can stay on the platform: it only redirects to the apex, whichever side serves it.
Retiring Pages (only after verification)
Business-site PR: remove the Pages workflow and its CNAME file and update the README receipt link. Then turn off SITE_PUBLICATION_ENABLED and unpublish the Pages site. The custom domain is not removed first. Removing it would let devantler-tech.github.io/business-site serve a second copy of the site.
Open: the two ownership markers external-dns wrote for www disappeared within a minute of creation. The cause is not yet known: it was not the Cloudflare repo's workflow, and no other external-dns writes this zone. www works but is not owned until the markers are back. devantler-tech/cloudflare recreates them next (reviewed handover list), and I watch them for five minutes.
Done: devantler.tech and www are served by the platform, and GitHub Pages is retired (15 November 2026)
Parity. All 305 public paths in both languages were crawled: pages, journal, tags, templates, assets, PDFs, RSS, sitemap, robots, historical redirects, the 404 page and the folder redirects. After business-site#584 (v3.3.0, #6315), every status code and redirect matches Pages. The only content difference at the origin is the build-time "Ranking checked" timestamp. The expected differences are /portal… redirecting to the portal host, the platform's /healthz, and the Pages-only publication receipt.
DNS hand-over (devantler-tech/cloudflare, declarative):
www → external-dns at 04:06 UTC (cloudflare#76). external-dns replaced the CNAME with gateway A/AAAA in one batch and owns them (_externaldns.a-www, _externaldns.aaaa-www).
The markers looked "missing" for a while; that was negative caching (SOA minimum 1800 s) after both sessions had queried those names before they existed, not a deletion.
Verified live after the switch: only Cloudflare addresses for both names; the platform is the origin; edge certificate valid to 2027-02-06; www and /about 301; http → https 301; branded 404; portal.devantler.tech/portal/ still 404; MX, SPF and the other mail records unchanged; external-dns quiet.
Pages retired: business-site#586 removed the Pages workflow, CNAME and its tests, and adds a check that refuses any workflow that deploys to Pages again. SITE_PUBLICATION_ENABLED is deleted and the Pages site is unpublished: devantler-tech.github.io/business-site/ and the Pages IPs answer 404, so nothing competes with the platform.
Left open, outside this issue:
Cloudflare's proxy rewrites the public HTML zone-wide: email obfuscation, bot JavaScript detections and an AI Labyrinth link. Pages-era visitors never got these. The Cloudflare repo session has put this to the maintainer because it changes bot protection for the whole zone.
The staging name business-site.platform.devantler.tech still serves the site. It can go now that the switch is done.
Leftovers for the maintainer to remove or keep: the github-pages environment and the COMPANY_POSTAL_ADDRESS secret in business-site, which no workflow uses any more.
Edge rewrites removed: visitors now get the origin's bytes (15 November, after 10:02 UTC)
devantler-tech/cloudflare#81 turned off email obfuscation, JavaScript detections and AI Labyrinth for the zone. A crawl of all 305 public paths through Cloudflare, compared with the platform origin directly:
304 paths match byte for byte with the same status code, including all pages, assets, feeds, redirects and the 404 page;
0 responses contain any injected Cloudflare markup;
the one difference is /.well-known/security.txt, which Cloudflare's managed security.txt serves (Contact: ned@devantler.tech) and the origin does not, as intended.
Activity
devantler commentedon Nov 13, 2026
Scope widened, 13 November 2026: devantler.tech moves onto the platform as well (devantler-tech/monorepo#3939).
devantler.techandwww.devantler.techbesideportal.devantler.tech, all from the cluster issuer.portal.devantler.techimmediately. The apex andwwwkeep pointing at Pages until the cutover hands their records to external-dns, because external-dns never overwrites a record it does not own.🤖 Generated with Claude Code
[-]Serve the business-site portal at portal.devantler.tech[/-][+]Serve devantler.tech and portal.devantler.tech from the platform[/+]devantler commentedon Nov 13, 2026
Progress and one blocker found on the way to the re-pin.
467f0758andd8b5d0e9for business-site, because Dependabot moved the caller off the approved revision. The canonical upgrade tooling also needs the v3.0.0 upgrade record settled first, and the daily regeneration that settles it has failed since 3 November for this reason and an identical aws drift (Restore complete publisher observations after AWS and Khoist caller transitions #5267).d8b5d0e9and stops Dependabot moving it. fix(cd): restore the platform-approved manifests publisher and keep it aws#81 does the same for aws. After both merge, the regeneration should pass. A business-site release on the approved publisher then lets this issue prepare its upgrade with the documented tooling.feat(business-site): move the tenant to its signed v3.2.1 release
fix(business-site): move the tenant to v3.2.2, signed by a publisher …
fix(business-site): list the approval being moved from first
devantler commentedon Nov 15, 2026
devantler.tech cutover: plan and rollback (written before any change)
Parity (15 November)
A crawl compared all 305 public paths on live Pages with the platform runtime (devantler.tech pinned to the gateway): English and Danish pages, journal, tags, templates, assets, PDFs, RSS, sitemap, robots and historical redirects. 289 match byte for byte. Content types match (JS is
text/javascriptinstead ofapplication/javascript, which is equivalent). Certificate on the gateway is valid fordevantler.tech,wwwandportal.Differences:
wwwanswered 302 (Pages: 301);/aboutwithout the slash answered 200 (Pages: 301 to/about/); a missing page showed plain text (Pages: the branded 404 page). The cutover waits for that release./portal…redirects to portal.devantler.tech, where the portal stays off (404)./healthzexists only on the platform. The Projects page shows a different "Ranking checked" date because Pages rebuilds daily.publication-source.jsonis the Pages publisher's own receipt; it goes with Pages.DNS hand-over (declarative, in devantler-tech/cloudflare; cloudflare#21)
The zone snapshot shows the apex is one flattened CNAME to
devantler.github.io(DNS-only), andwwwa proxied CNAME to the same target. That makes the switch two small changes, neither with a gap and neither changing external-dns's configuration (#6312, option 2):www→ external-dns. devantler-tech/cloudflare creates the marker_externaldns.cname-www.devantler.techwith contentheritage=external-dns,external-dns/owner=platform.devantler.tech,external-dns/resource=httproute/business-site/business-site-public, and drops thewwwCNAME from its state (destroy=false). Within a minute external-dns deletes the CNAME and creates proxied gateway A/AAAA records in one Cloudflare batch, which is a single transaction.www. Afterwwwis verified on the gateway, devantler-tech/cloudflare edits the apex CNAME in place towww.devantler.tech, proxied. A single record edit means no gap, and the apex then follows the gateway throughwwwwith no manual step.The apex MX, SPF, Apple, DMARC, DKIM and Pages-challenge records stay as they are in OpenTofu. external-dns plans no apex change today, after B or after C (checked with external-dns v0.23.0's registry and planner on a zone of this shape), so
devantler.techstays in the HTTPRoute, where the gateway needs it.During the switch, resolvers that cached the old answers (five-minute TTL) still reach Pages, which serves the same pages.
Verification (agent, right after)
Public DNS shows only Cloudflare addresses for both names. The crawl is re-run against live DNS: every path matches, certificates are valid,
wwwand plain HTTP give 301, and portal.devantler.tech/portal/ is still 404.Rollback (until Pages is retired)
Pages keeps its custom domain and certificate (valid to 2027-01-04) until verification passes.
devantler.github.iowith proxy off. One edit, no gap.wwwcan stay on the platform: it only redirects to the apex, whichever side serves it.Retiring Pages (only after verification)
Business-site PR: remove the Pages workflow and its
CNAMEfile and update the README receipt link. Then turn offSITE_PUBLICATION_ENABLEDand unpublish the Pages site. The custom domain is not removed first. Removing it would letdevantler-tech.github.io/business-siteserve a second copy of the site.🤖 Generated with Claude Code
devantler commentedon Nov 15, 2026
Cutover progress, 15 November ~04:30 UTC
/healthzand Pages-receipt differences.wwwdisappeared within a minute of creation. The cause is not yet known: it was not the Cloudflare repo's workflow, and no other external-dns writes this zone.wwwworks but is not owned until the markers are back. devantler-tech/cloudflare recreates them next (reviewed handover list), and I watch them for five minutes.www.devantler.tech, proxied (Let the devantler.tech apex record follow the gateway without a manual step #6312, option 2). Rollback is the same edit back todevantler.github.io, unproxied.🤖 Generated with Claude Code
ci(pages): retire the GitHub Pages publication (#586)
devantler commentedon Nov 15, 2026
Done: devantler.tech and www are served by the platform, and GitHub Pages is retired (15 November 2026)
Parity. All 305 public paths in both languages were crawled: pages, journal, tags, templates, assets, PDFs, RSS, sitemap, robots, historical redirects, the 404 page and the folder redirects. After business-site#584 (v3.3.0, #6315), every status code and redirect matches Pages. The only content difference at the origin is the build-time "Ranking checked" timestamp. The expected differences are
/portal…redirecting to the portal host, the platform's/healthz, and the Pages-only publication receipt.DNS hand-over (devantler-tech/cloudflare, declarative):
www→ external-dns at 04:06 UTC (cloudflare#76). external-dns replaced the CNAME with gateway A/AAAA in one batch and owns them (_externaldns.a-www,_externaldns.aaaa-www).www.devantler.tech, proxied, so the apex follows the gateway throughwww(Let the devantler.tech apex record follow the gateway without a manual step #6312). No gap at either step, and the mail records were never touched.Verified live after the switch: only Cloudflare addresses for both names; the platform is the origin; edge certificate valid to 2027-02-06;
wwwand/about301; http → https 301; branded 404; portal.devantler.tech/portal/ still 404; MX, SPF and the other mail records unchanged; external-dns quiet.Pages retired: business-site#586 removed the Pages workflow,
CNAMEand its tests, and adds a check that refuses any workflow that deploys to Pages again.SITE_PUBLICATION_ENABLEDis deleted and the Pages site is unpublished:devantler-tech.github.io/business-site/and the Pages IPs answer 404, so nothing competes with the platform.Left open, outside this issue:
business-site.platform.devantler.techstill serves the site. It can go now that the switch is done.github-pagesenvironment and theCOMPANY_POSTAL_ADDRESSsecret in business-site, which no workflow uses any more.🤖 Generated with Claude Code
devantler commentedon Nov 15, 2026
Edge rewrites removed: visitors now get the origin's bytes (15 November, after 10:02 UTC)
devantler-tech/cloudflare#81 turned off email obfuscation, JavaScript detections and AI Labyrinth for the zone. A crawl of all 305 public paths through Cloudflare, compared with the platform origin directly:
/.well-known/security.txt, which Cloudflare's managed security.txt serves (Contact: ned@devantler.tech) and the origin does not, as intended.That closes the last open item above.
🤖 Generated with Claude Code