fix: update docker file paths and context in branch build workflow

[sriramveeraghanta]

Description

• Update docker file paths and context in branch build workflow

Type of Change

• Bug fix (non-breaking change which fixes an issue)

Summary by CodeRabbit

• Chores
  • Updated workflow configuration to use new file paths for Dockerfiles and build contexts when building Docker images.

[coderabbitai]

Walkthrough

The workflow configuration for building and pushing Docker images was updated to use new Dockerfile locations and build contexts under the ./apps directory. The changes only affect file paths within the workflow and do not modify logic, environment variables, or any public code entities.

Changes

File(s)	Change Summary
.github/workflows/build-branch.yml	Updated Dockerfile paths and build contexts for admin, web, space, live, and backend images to use new ./apps/... subdirectories.

Possibly related PRs

• fix: dockerfile build paths #7322: Updates Docker build paths to match the /apps directory structure, directly related to the workflow path changes in this PR.

Poem

🐇
In the warren of code, new paths appear,
Dockerfiles moved, their purpose clear.
From top to apps, the journey’s made,
Build scripts updated, progress displayed.
With every hop, the workflow’s neat—
Now Docker’s dance is more complete!

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/build-branch.yml (1)

135-137: Narrow build-context to the component directory for faster, lighter builds

The Dockerfiles have moved under ./apps/**, but build-context is still . for Admin, Web, Space and Live images.
Sending the whole repo (sometimes > 100 MB) to Docker unnecessarily increases cache misses and CI run-time.

Optional refactor:

-          build-context: .
+          build-context: ./apps/admin      # similarly web/space/live below

Repeat the same adjustment for the other three blocks (web, space, live).

If the Dockerfiles rely on files outside their folder, keep the wider context, otherwise this change is a free win in performance and network traffic.

Also applies to: 157-159, 179-181, 201-203

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 021b6ee and cdab2a4.

📒 Files selected for processing (1)

• .github/workflows/build-branch.yml (5 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: Build-Push API Server Docker Image
• GitHub Check: Build-Push Web Docker Image
• GitHub Check: Build-Push Space Docker Image
• GitHub Check: Build-Push Live Collaboration Docker Image
• GitHub Check: Build-Push Admin Docker Image
• GitHub Check: Analyze (javascript)