feat: Adding Docker CMD in all Dockerfiles

[sriramveeraghanta]

Type of Change

• Feature (non-breaking change which adds functionality)

Summary by CodeRabbit

• Chores
  • Added default startup commands to container images for admin, live, API, space, and web applications, ensuring each service automatically starts its server when the container launches.

[coderabbitai]

Walkthrough

Default startup commands were added to the Dockerfiles for the admin, live, server (API), space, and web applications. Each Dockerfile now includes a CMD instruction to specify which server script or entrypoint should run when the container starts. No changes to application code or exported entities were made.

Changes

Files	Summary of Changes
apps/admin/Dockerfile.admin	Added CMD to run node apps/admin/server.js on container start
apps/live/Dockerfile.live	Added CMD to run node live/server.js on container start
apps/server/Dockerfile.api	Added CMD to run ./bin/docker-entrypoint-api.sh on start
apps/space/Dockerfile.space, apps/web/Dockerfile.web	Added CMD to run respective server.js files on container start

Suggested reviewers

• prateekshourya29
• Prashant-Surya

Poem

The Dockerfiles now know what to do,
When launched, they spring up—no need for a cue!
Each app starts its server, neat and precise,
Containers awaken—oh, isn’t that nice?
🐇 With a hop and a skip, the servers all run,
Ready for traffic, the work is well done!

---

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: 0

🧹 Nitpick comments (2)

apps/server/Dockerfile.api (1)

52-52: Ensure entrypoint script forwards signals with exec
Good to see a dedicated CMD. Confirm that bin/docker-entrypoint-api.sh ends with exec "$@" (or an equivalent) so SIGTERM/SIGINT reach the Python/uvicorn process; otherwise Kubernetes & Docker stop signals will be swallowed.

apps/web/Dockerfile.web (1)

109-111: Path consistency across workspaces
Here we run node apps/web/server.js, whereas the live image uses node live/server.js. The difference is intentional (due to the pruning layout), but the inconsistency is easy to trip over later. Consider normalising to either apps/<name>/… everywhere or adding a brief comment explaining the rationale.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 805cfed and 474035f.

📒 Files selected for processing (5)

• apps/admin/Dockerfile.admin (1 hunks)
• apps/live/Dockerfile.live (1 hunks)
• apps/server/Dockerfile.api (1 hunks)
• apps/space/Dockerfile.space (1 hunks)
• apps/web/Dockerfile.web (1 hunks)

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

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

🔇 Additional comments (3)

apps/live/Dockerfile.live (1)

54-56: Verify port & path alignment with runtime server
EXPOSE 3000 + node live/server.js presumes the compiled live service is actually listening on port 3000 and that the server entry lives at /app/live/server.js in the final image. Please double-check these two assumptions; a mismatch will result in the container starting but failing health checks.

apps/admin/Dockerfile.admin (1)

92-94: LGTM – explicit startup command added
Defining the default CMD removes the need for docker run … node … overrides. No issues spotted.

apps/space/Dockerfile.space (1)

92-94: LGTM – container now self-starts
The added CMD correctly targets the Next.js standalone output; looks good.