[codex] move staging site to new domain#108
Conversation
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey - I've found 2 issues, and left some high level feedback:
- Consider moving the staging vs production Pro URL logic out of
global.astrointo a shared configuration or environment-based mapping so domain changes don’t require code edits in the layout. - In
update-00.mdx, there are a couple of minor text issues (e.g., the double “now” in “Now you can now arbitrarily connect…” and the typo “extrordinaire”) that you may want to clean up for readability.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- Consider moving the staging vs production Pro URL logic out of `global.astro` into a shared configuration or environment-based mapping so domain changes don’t require code edits in the layout.
- In `update-00.mdx`, there are a couple of minor text issues (e.g., the double “now” in “Now you can now arbitrarily connect…” and the typo “extrordinaire”) that you may want to clean up for readability.
## Individual Comments
### Comment 1
<location path="src/pages/blog/update-00.mdx" line_range="5" />
<code_context>
title: Update 00
author: kixelated
-description: Update 00 notes
+description: Multiple months of patch notes extrordinaire for your eyeballs.
cover: "/blog/update-00/bbb.png"
date: 2026-06-25
</code_context>
<issue_to_address>
**nitpick (typo):** Typo in description text: "extrordinaire" should be "extraordinaire".
This misspelling will show up in the blog metadata and previews; please correct it to "extraordinaire."
```suggestion
description: Multiple months of patch notes extraordinaire for your eyeballs.
```
</issue_to_address>
### Comment 2
<location path="src/pages/blog/update-00.mdx" line_range="19-21" />
<code_context>
## Hop-based Routing
-Now you can [connect relays to each other](https://doc.moq.dev/bin/relay/) however you desire.
+Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path.
</code_context>
<issue_to_address>
**nitpick (typo):** Redundant wording with "Now you can now" in the routing section.
Please adjust this sentence to remove the duplicated "now" (e.g., "Now you can arbitrarily connect..." or "You can now arbitrarily connect...") for smoother readability.
```suggestion
## Hop-based Routing
Now you can arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster.
They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path.
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
| title: Update 00 | ||
| author: kixelated | ||
| description: Update 00 notes | ||
| description: Multiple months of patch notes extrordinaire for your eyeballs. |
There was a problem hiding this comment.
nitpick (typo): Typo in description text: "extrordinaire" should be "extraordinaire".
This misspelling will show up in the blog metadata and previews; please correct it to "extraordinaire."
| description: Multiple months of patch notes extrordinaire for your eyeballs. | |
| description: Multiple months of patch notes extraordinaire for your eyeballs. |
| ## Hop-based Routing | ||
| Now you can [connect relays to each other](https://doc.moq.dev/bin/relay/) however you desire. | ||
| Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster. | ||
| They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path. |
There was a problem hiding this comment.
nitpick (typo): Redundant wording with "Now you can now" in the routing section.
Please adjust this sentence to remove the duplicated "now" (e.g., "Now you can arbitrarily connect..." or "You can now arbitrarily connect...") for smoother readability.
| ## Hop-based Routing | |
| Now you can [connect relays to each other](https://doc.moq.dev/bin/relay/) however you desire. | |
| Now you can now arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster. | |
| They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path. | |
| ## Hop-based Routing | |
| Now you can arbitrarily connect [moq-relay](https://doc.moq.dev/bin/relay/) instances to each other to form a cluster. | |
| They'll gossip available broadcasts to each other and proxy any subscriptions automatically via the shortest path. |
|
Warning Review limit reached
Next review available in: 52 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. WalkthroughThis change updates the staging environment's route pattern in wrangler.jsonc from moq.wtf to cdn.moq.wtf, with no other configuration changes. It also modifies the Markdown table formatting in the update-00 blog post by adjusting the header separator row under the "Bitrate savings for different configurations" section, affecting table rendering without altering other content. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/pages/blog/update-00.mdx`:
- Line 5: The frontmatter description contains a typo in the blog page metadata.
Update the description text in the markdown frontmatter so that the word
“extrordinaire” is corrected to “extraordinaire” in the update-00 content.
- Line 20: The sentence in the blog post has a duplicated “now” in the opening
phrase. Update the wording in the MDX content so the lead-in reads either “Now
you can” or “You can now” while keeping the rest of the moq-relay sentence
unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 3e836e55-88eb-49e3-a54b-7dc848d1aa03
📒 Files selected for processing (3)
src/layouts/global.astrosrc/pages/blog/update-00.mdxwrangler.jsonc
468afc0 to
f05685c
Compare
1 participant
Summary
moq.wtftonew.moq.devhttps://moq.wtfand live/local points tohttps://moq.proupdate-00patch-note editsWhy
moq.wtfis being repurposed, so the staging site needs to live atnew.moq.devwhile the Pro link takes over the old staging domain. The existing local patch-note updates are included in the same PR by request.Validation
bun run checkbun astro build --mode stagingNote:
bun run checkreports the existing Biome config deprecation info forrecommended; no check failures.