Test api ci

[Behzad-rabiei]

Summary by CodeRabbit

• Chores

  • Adjusted the application’s production startup configuration to ensure smooth, reliable launches by reinstating the proper startup command and simplifying the testing setup.

• Style

  • Refined the server’s startup log message for clearer, more concise output during initialization.

[coderabbitai]

Walkthrough

This pull request updates two components. In the Dockerfile, the production stage now explicitly includes the command to start the Node.js application and the testing stage has been removed, while the development stage remains the same. In the main server file, the log message in the bootstrap function has been adjusted to use a single exclamation mark instead of two.

Changes

File	Summary
api/Dockerfile	Reintroduced CMD ["node", "dist/main"] in production stage; removed the testing stage.
api/src/main.ts	Modified log message in the bootstrap function, reducing exclamation marks from two to one.

Poem

Oh, I hop with glee in the code,
Changes bounce like carrots in a row,
Commands restored and tests set free,
A single shout in logs now shows,
Leaping ahead in bytes, let the new code glow! 🐇✨

---

📜 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 d3f402f and e738cfa.

📒 Files selected for processing (2)

• api/Dockerfile (1 hunks)
• api/src/main.ts (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• api/src/main.ts

🔇 Additional comments (1)

api/Dockerfile (1)

25-25: CMD command explicit in Production Stage
The addition of the CMD ["node", "dist/main"] in the production stage clearly specifies how to start the Node.js application in production. This change aligns well with the PR objective to improve the CI setup and ensures that the container is self-sufficient for running the production build.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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. (Beta)
• @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.