feat(infra): wire loopover.ai as a live secondary domain#5345
Merged
Conversation
Adds loopover.ai (UI) and api.loopover.ai (API) as custom-domain routes alongside the existing gittensory.aethereal.dev domains, live side by side with no cutover yet. Introduces PUBLIC_SITE_ORIGIN_ALIASES so the post-GitHub-OAuth-login redirect works correctly from either domain -- without it, a login started on loopover.ai would authenticate but bounce back to the old domain, since PUBLIC_SITE_ORIGIN only ever supported a single allowed origin.
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
gittensory-ui | e7142fa | Commit Preview URL Branch Preview URL |
Jul 12 2026, 02:23 PM |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5345 +/- ##
==========================================
- Coverage 94.40% 94.36% -0.04%
==========================================
Files 550 550
Lines 44116 44118 +2
Branches 14631 14632 +1
==========================================
- Hits 41649 41634 -15
- Misses 1792 1809 +17
Partials 675 675
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
loopover.ai(UI Worker) andapi.loopover.ai(API Worker) as custom-domain routes, live side by side with the existinggittensory.aethereal.devdomains -- no cutover, no redirect yet.PUBLIC_SITE_ORIGIN_ALIASES(comma-separated, config-driven) so the post-GitHub-OAuthreturnToredirect works correctly from either domain. Without it,normalizeReturnTo's allowlist only ever contained the singlePUBLIC_SITE_ORIGINvalue, so a login started onloopover.aiwould authenticate fine but bounce back to the old domain on completion.Test plan
npm run typechecknpm run test:ci(full local gate, green)PUBLIC_SITE_ORIGIN_ALIASES: primary origin still works, an aliased origin is accepted verbatim, a second comma-separated alias works, an untrusted origin still falls back, and unset-alias behavior is unchanged from before this var existedloopover.aiandapi.loopover.airesolve over TLS once the custom domains provision, and complete a real GitHub OAuth sign-in fromloopover.aiend-to-endCloses #4762.