Skip to content

Move the portal off the bare domain to apps.<domain> - #14

Merged
tytremblay merged 1 commit into
mainfrom
move-portal-to-apps-subdomain
Aug 22, 2026
Merged

tytremblay merged 1 commit into
mainfrom
move-portal-to-apps-subdomain

Conversation

@tytremblay

Copy link
Copy Markdown
Contributor

Part of moving off DuckDNS to redhawkrobotics.org, whose root is the team website on Google Sites. The stack must not claim the bare domain, so:

  • Caddyfile: portal block moves from {$DOMAIN} to apps.{$DOMAIN}; the bare domain is now never served. CADDY_CONFIG_REV bumped so the routing change recreates Caddy on deploy.
  • portal/index.html: links were built from window.location.host, which at apps.<domain> would have produced shop.apps.<domain>. The portal now strips its own apps. label first.
  • deploy.yml: portal health check now hits https://apps.${DOMAIN}.
  • Docs, .env.example, setup.sh banner, README, PLAN.md, CLAUDE.md updated to match.

The DOMAIN repository variable is already set to redhawkrobotics.org, and A records for apps/shop/mod/bot point at the Linode. Deploy is manual dispatch, so nothing changes until this merges and a deploy is approved. After that deploy, the Slack (mod/bot) and Onshape (shop) registrations still need their URLs updated — the old duckdns endpoints stop routing at cutover.

🤖 Generated with Claude Code

The suite is moving from hawksuite.duckdns.org to redhawkrobotics.org,
whose root is the team website on Google Sites. Nothing in the stack may
claim the bare domain, so the portal moves to apps.<domain> and the bare
domain is now never served. The portal's links derive from its own
hostname, so it strips its "apps." label before building the shop/mod/bot
URLs. CADDY_CONFIG_REV bumped so the routing change actually recreates
Caddy on deploy.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@tytremblay
tytremblay merged commit da16ec1 into main Aug 22, 2026
1 check passed
@rachmo
rachmo deleted the move-portal-to-apps-subdomain branch September 26, 2026 22:52
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