Skip to content

Serve devantler.tech and portal.devantler.tech from the platform #6177

Closed
1 of 1 issue completed
Closed

Description

@devantler

Why

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.
  • Re-pin: move the business-site Tenant to the new signed release that carries the portal host. That release is Serve the portal at portal.devantler.tech business-site#554.
  • DNS: nothing to add. The platform's external-dns already manages the devantler.tech zone, so it creates the portal record from the route.

Done when

https://portal.devantler.tech/ reaches the business-site app with a valid certificate, the staging name is gone, and the portal stays default-off.

Part of devantler-tech/monorepo#3939.

🤖 Generated with Claude Code

Activity

  1. moved this to 📥 Backlog in 🌊 Project Boardon Nov 13, 2026
  2. devantler commented on Nov 13, 2026

    @devantler
    ContributorAuthor

    Scope widened, 13 November 2026: devantler.tech moves onto the platform as well (devantler-tech/monorepo#3939).

    • 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.

    🤖 Generated with Claude Code

  3. 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
  4. devantler commented on Nov 13, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Progress and one blocker found on the way to the re-pin.

  5. devantler commented on Nov 15, 2026

    @devantler
    ContributorAuthor

    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.

    Differences:

    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.

    🤖 Generated with Claude Code

  6. devantler commented on Nov 15, 2026

    @devantler
    ContributorAuthor

    Cutover progress, 15 November ~04:30 UTC

    🤖 Generated with Claude Code

  7. devantler commented on Nov 15, 2026

    @devantler
    ContributorAuthor

    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).
    • Apex at 04:58 UTC (cloudflare#79): the flattened CNAME was edited in place to www.devantler.tech, proxied, so the apex follows the gateway through www (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.
    • 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.

    🤖 Generated with Claude Code

  8. moved this from 📥 Backlog to ✅ Done in 🌊 Project Boardon Nov 15, 2026
  9. devantler commented on Nov 15, 2026

    @devantler
    ContributorAuthor

    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.

    That closes the last open item above.

    🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    Priority

    None yet

    Start date

    None yet

    Target date

    None yet

    Effort

    None yet

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions