Repository navigation
feat!: move to r9lab.io and rename the product to R9lab - #417
Merged
Merged
Conversation
- rename the auth, refresh and OAuth CSRF cookies to __Host-r9lab-auth, __Host-r9lab-refresh and __Host-r9lab-oauth-csrf - the old names are no longer read, so existing sessions end once - regenerate the public OpenAPI schema and the app API types
The old zone's redirect ruleset covered both environments, so cutting over staging also redirected the prod hosts to names that do not exist yet. redirect_environments (default both) limits the rules to the environments being moved.
An unknown environment produced no routes, so the check passed with nothing tested. It now exits 2 before any request.
The edge root defaults to r9lab.io, so an old zone id left in the environment would put the records in the wrong zone. The plan now fails when the id and name disagree.
- cover both zones in the two-roots overview, with one zone-root workspace per zone - add the redirect cutover per environment, the pre-window ruleset check and the post-cutover tfvars - state the expected plan after the first-run state move, and the case where the workspace exists - apply the new zone's rulesets before its records, and keep a proxied record on the old zone - add the token rows for redirects, Email Routing and the zone id check
- write "an R9lab" in the duplicate-account email and the codebook description - join the split Changed list and drop a maintainer-only note - note the per-environment redirects and the edge root's zone id check
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
- point the .github pages at docs.r9lab.io and the info@r9lab.io contact - rename the product to R9lab in those pages and the devcontainer greetings - add a test that keeps README.md and the .github pages off the old domain
- redirect_environments has no default and must be set whenever redirect_to_zone_name is, so a staging apply cannot redirect prod by leaving it out - legacy_zone_name defaults to the previous zone during the move, so an apply without it keeps the old hosts in the tunnel ingress - commit the old zone's tfvars as each environment's redirects land
After a correct first hop, request the new host once more and fail when it redirects back to the old zone, which a leftover forwarding rule on the new zone would do.
- assert every old host redirects to its own prefix on the new zone, from literal pairs - check that the smoke script's host list matches infra/cloudflare/hostnames.tf
A zone with email_forwards also gets a _dmarc TXT record with p=none and aggregate reports to info@ on that zone. DKIM and SPF for outbound mail stay with the sending provider.
- run the zone move per environment: remove the interim forwarding for its hosts right before its edge apply, and build images only after that apply - keep the cutover window to one YES: plan the redirect apply right before the .env switch, check the Environment's API_PUBLIC_URL, run Deploy Sites, then apply - roll back the Environment URL variables by hand, since the old records are unmanaged - apply the moved old-zone state's description-only plan at the state move
- the committed old-zone tfvars overrides TF_VAR_*, so prod's redirect apply edits it to both environments and commits the edit once the apply lands - keep the placeholder records and narrow the interim redirect rules to the prod hosts before staging's edge apply, so prod hosts keep forwarding until their own apply - describe redirect_environments as an empty default with a validation
* origin/main: feat(app): expand the component tree to any depth with a weight total (#416) test(backend): pin clamav protocol and upload quota ledger results (#415) fix(app): remove two traps from the next Expo and React Native upgrade (#414) # Conflicts: # CHANGELOG.md # app/src/types/openapi.json
simonvanlierde
added a commit
that referenced
this pull request
Oct 10, 2026
…ertions * origin/main: feat!: move to r9lab.io and rename the product to R9lab (#417) # Conflicts: # backend/tests/integration/api/auth/test_oauth_callbacks.py
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
2 participants
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.
Moves the public domain to r9lab.io and renames the product to R9lab in all user-facing text.
cml-relab.orgkeeps working through redirects, and existing sessions end once because the session cookies are renamed.info@is forwarded with Email Routing. The edge serves r9lab.io, keeping the old tunnel hostnames in its ingress during the switch.__Host-r9lab-*; the old names are no longer accepted.just smoke-redirectschecks the redirects after each cutover step.Part of #410.