feat: optimize docker builds for live server

[sriramveeraghanta]

Description

• Optimized the docker build for live server.

Type of Change

• Feature (non-breaking change which adds functionality)

Summary by CodeRabbit

• Chores
  • Updated the Dockerfile structure for improved clarity with labeled build stages and enhanced comments.
  • Adjusted environment variable formatting for consistency.
  • Refined file copying during the build process to include only necessary directories and files.

[coderabbitai]

Walkthrough

The Dockerfile for the apps/live project was reorganized into three explicit build stages with improved comments. Adjustments were made to environment variable syntax, and the final stage now copies only necessary subdirectories and files instead of the entire application directory. No changes were made to exported or public entities.

Changes

File(s)	Change Summary
apps/live/Dockerfile.live	Restructured into three labeled stages, updated comments, standardized environment variable syntax, and refined file copy instructions in the final stage.

Possibly related PRs

• fix: dockerfile build paths #7322: Restructures Dockerfiles for other apps, standardizing build stages and environment variable usage, and updates file copy paths, mirroring the approach in this PR.

Poem

In Docker’s warren, neat and bright,
Three stages now—what a sight!
Pruned and built, then run with care,
Only what’s needed, we copy there.
A tidy burrow, swift and lean,
For every rabbit and their machine! 🐇

---

📜 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 d29d2b6 and 252bc44.

📒 Files selected for processing (1)

• apps/live/Dockerfile.live (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/live/Dockerfile.live

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

• GitHub Check: Analyze (javascript)
• GitHub Check: Analyze (python)

---

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

🔭 Outside diff range comments (1)

apps/live/Dockerfile.live (1)

45-56: Container lacks a default start command

The final stage exposes port 3000 but defines neither CMD nor ENTRYPOINT; the container will exit immediately unless an external command is provided. Add a sensible default to improve DX and avoid silent failures in CI/CD.

 EXPOSE 3000
+
+# Start the live server
+CMD ["node", "apps/live/dist/index.js"]

🧹 Nitpick comments (2)

apps/live/Dockerfile.live (2)

23-24: Merge Alpine package operations to reduce layers

apk update followed by apk add produces an extra, cache-invalidating layer. Combine them to keep the image smaller and cache-friendly.

-RUN apk update
-RUN apk add --no-cache libc6-compat
+RUN apk add --no-cache --update libc6-compat

---

31-33: Use a reproducible, production-lean install

Running plain yarn install pulls dev dependencies that later get copied into the runtime image. Lock the install and trim dev-only packages to keep the final image slim.

-RUN yarn install
+RUN yarn install --frozen-lockfile --production=false
+# After build:
+# RUN yarn workspaces focus --production

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6f27ec0 and d29d2b6.

📒 Files selected for processing (1)

• apps/live/Dockerfile.live (3 hunks)

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

• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript)