Skip to content

build: add frontend to docker compose#131

Merged
HeadHunter483 merged 2 commits into
mainfrom
0-frontend-docker-compose
Sep 14, 2025
Merged

build: add frontend to docker compose#131
HeadHunter483 merged 2 commits into
mainfrom
0-frontend-docker-compose

Conversation

@almostxyz
Copy link
Copy Markdown
Contributor

@almostxyz almostxyz commented Sep 14, 2025

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #(issue)


  • I have read and followed all requirements in CONTRIBUTING.md;
  • I used LLM/AI assistance to make this pull request;

If you have used LLM/AI assistance please provide model name and full prompt:

Model: {{model-name}}
Prompt: {{prompt}}

Summary by CodeRabbit

  • New Features
    • Enabled cross-origin requests from all origins to simplify integrations.
    • Increased maximum search results to 100 for broader result sets.
  • Chores
    • Added a frontend service to the quickstart; exposes port 5173 for local access.
    • Introduced a configurable database timeout (default 15s) to improve reliability.

@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Sep 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.49%. Comparing base (09d9579) to head (33d2553).
⚠️ Report is 142 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #131      +/-   ##
==========================================
- Coverage   71.50%   71.49%   -0.02%     
==========================================
  Files         201      201              
  Lines       18170    18170              
==========================================
- Hits        12993    12991       -2     
- Misses       4457     4459       +2     
  Partials      720      720              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Sep 14, 2025

📝 Walkthrough

Walkthrough

Adds new CORS, DB timeout, and API limit settings to the seq-ui quickstart config, and introduces a new frontend service in the docker-compose file mapping port 5173 to container port 80.

Changes

Cohort / File(s) Summary of Changes
Seq UI config updates
quickstart/config.seq-ui.yaml
Added server.cors with allowed_origins, allowed_methods (OPTIONS, HEAD, GET, POST, PUT, PATCH, DELETE), and allowed_headers; added clients.seq_db_timeout: 15s; added handlers.seq_api.max_search_limit: 100.
Docker compose additions
quickstart/docker-compose.seq-ui.yaml
Added seq-ui-fe service using ghcr.io/ozontech/seq-ui-fe:latest, exposing 5173:80.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • ssnd
  • moflotas

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "build: add frontend to docker compose" accurately and concisely captures the primary change — adding the frontend service to the Docker Compose setup; the diff shows a new seq-ui-fe service in quickstart/docker-compose.seq-ui.yaml and related config updates (CORS and public settings) to support it, so the title is on-point and not misleading. It is short, specific, and follows a conventional commit-style prefix.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 0-frontend-docker-compose

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d3e66ff and 33d2553.

📒 Files selected for processing (1)
  • quickstart/config.seq-ui.yaml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • quickstart/config.seq-ui.yaml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: test

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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 and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 09d9579 and d3e66ff.

📒 Files selected for processing (2)
  • quickstart/config.seq-ui.yaml (1 hunks)
  • quickstart/docker-compose.seq-ui.yaml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: test
🔇 Additional comments (1)
quickstart/docker-compose.seq-ui.yaml (1)

11-14: Pin image tag and confirm FE→API wiring

File: quickstart/docker-compose.seq-ui.yaml Lines: 11-14

  • Parameterize the image tag to avoid using :latest in CI/deployments. Suggested diff:
-    image: ghcr.io/ozontech/seq-ui-fe:latest
+    image: ghcr.io/ozontech/seq-ui-fe:${SEQ_UI_FE_TAG:-latest}
+    # If the image supports runtime envs, consider wiring API base URL explicitly:
+    # environment:
+    #   - API_BASE_URL=http://seq-ui:5555
  • Confirm how the FE resolves the API base URL (env/config/reverse-proxy). If FE is served from a different origin and CORS is open, ensure it targets seq-ui:5555 or use a reverse proxy to avoid cross-origin calls.

Comment thread quickstart/config.seq-ui.yaml
Comment thread quickstart/config.seq-ui.yaml
@HeadHunter483 HeadHunter483 merged commit 688a847 into main Sep 14, 2025
11 checks passed
@HeadHunter483 HeadHunter483 deleted the 0-frontend-docker-compose branch September 14, 2025 11:29
@coderabbitai coderabbitai Bot mentioned this pull request Sep 14, 2025
2 tasks
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.

5 participants