Skip to content

docs: add frontend dev server config to CORS section#518

Merged
cte merged 4 commits intomainfrom
cte/cors-docs-update
Jan 29, 2026
Merged

docs: add frontend dev server config to CORS section#518
cte merged 4 commits intomainfrom
cte/cors-docs-update

Conversation

@cte
Copy link
Collaborator

@cte cte commented Jan 29, 2026 •
edited by ellipsis-dev bot
Loading

Important

Updates environments.mdx to include frontend dev server configuration for CORS handling in preview environments.

  • Documentation Update:
    • Adds frontend dev server configuration to CORS section in environments.mdx.
    • Details backend CORS configuration using ROO_WEB_HOST for Express, Hono, and Fastify.
    • Provides frontend configuration examples for Vite and Next.js to allow preview domains.

This description was created by Ellipsis for 777f963. You can customize this summary. It will automatically update as commits are pushed.

cte and others added 3 commits January 29, 2026 10:29
@cte @claude
docs: add frontend dev server config to CORS section
e5ec610 
Cover both sides of CORS in preview environments: backend origin
allowlisting and frontend dev server host configuration (Vite
allowedHosts, Next.js allowedDevOrigins).

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cte @claude
docs: use specific allowedHosts for Vite instead of true
f51de82 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@cte @claude
docs: use ROO_WEB_HOST for frontend allowedHosts config
777f963 
Extract hostname from the full URL for Vite's allowedHosts, and use
the env var directly for Next.js allowedDevOrigins.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@vercel
Copy link

vercel bot commented Jan 29, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
roo-code-docs Ready Ready Preview, Comment Jan 29, 2026 8:01pm

Request Review

@roomote
Copy link
Contributor

roomote bot commented Jan 29, 2026 •
edited
Loading

Rooviewer Clock   See task on Roo Cloud

Review complete. No issues found.

The PR correctly adds frontend dev server configuration to the CORS section, covering both Vite (allowedHosts) and Next.js (allowedDevOrigins). The examples properly use ROO_WEB_HOST with appropriate fallbacks for local development.

Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.

@cte cte merged commit 4cba3f5 into main Jan 29, 2026
2 of 3 checks passed
@cte cte deleted the cte/cors-docs-update branch January 29, 2026 20:00
@github-project-automation github-project-automation bot moved this from Triage to Done in Roo Code Roadmap Jan 29, 2026
@roomote
Copy link
Contributor

roomote bot commented Jan 29, 2026 •
edited
Loading

Rooviewer Clock   See task on Roo Cloud

Review complete. No issues found.

The PR correctly adds frontend dev server configuration to the CORS section, covering both Vite (allowedHosts with hostname extraction) and Next.js (allowedDevOrigins). The examples properly use ROO_WEB_HOST with appropriate fallbacks for local development.

Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.

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

Reviewers

@roomote roomote[bot] roomote[bot] approved these changes

@mrubens mrubens Awaiting requested review from mrubens mrubens is a code owner

@hannesrudolph hannesrudolph Awaiting requested review from hannesrudolph hannesrudolph is a code owner

Assignees

No one assigned

Labels

None yet

Projects

No open projects
Roo Code Roadmap
Status: Done

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@cte