Skip to content

chore: serve client as static build via nginx#108

Merged
memreo merged 2 commits into
mainfrom
chore/client-static-build
Jul 2, 2026
Merged

chore: serve client as static build via nginx#108
memreo merged 2 commits into
mainfrom
chore/client-static-build

Conversation

@memreo

@memreo memreo commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

Client ran the Vite dev server in production, which also blocks unknown Host headers (breaks the new ingress from #107). Switched to a multi-stage build: vite build then serve dist/ via nginx. Dropped the now-unused VITE_API_BASE_URL runtime env from client.yaml.

Component

  • Client: client/
  • Infrastructure: infra/

API Impact

  • This does not change the API.

Testing

  • I tested this locally (build + docker run, checked SPA fallback and foreign Host header).

Checklist

  • Branch name follows (feat|fix)/(issue_id)/(name_of_issue) — no issue, descriptive name used.
  • The change is limited to the intended component(s).

Related Issue

No related issue.

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@memreo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 45 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 76f133f7-5859-42b1-a74d-3dd47e7cc9f6

📥 Commits

Reviewing files that changed from the base of the PR and between 7d3abfb and 0206177.

⛔ Files ignored due to path filters (1)
  • client/public/favicon.svg is excluded by !**/*.svg
📒 Files selected for processing (4)
  • client/Dockerfile
  • client/index.html
  • client/nginx.conf
  • infra/k8s/client.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/client-static-build

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@memreo memreo requested a review from sachmii July 2, 2026 16:06

@sachmii sachmii left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for implementing

@memreo memreo merged commit 94becd2 into main Jul 2, 2026
25 checks passed
sachmii pushed a commit that referenced this pull request Jul 2, 2026
chore: serve client as static build via nginx
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.

2 participants