feat: add docker and docker-compose file

[ramraut-osm]

API PR Checklist

Pre-requisites

• I have gone through the Contributing guidelines for Submitting a Pull Request (PR) and ensured that this is not a duplicate PR.
• I have performed preliminary unit testing.
• I have updated the required api docs as applicable.
• I have added/updated test cases to the test suite as applicable

PR Details

PR details have been updated as per the given format (see below)

• PR title adheres to the format specified in guidelines (e.g., feat: add admin login endpoint)
• Description has been added
• Related changes have been added (optional)
• Screenshots have been added (optional)
• Query request and response examples have been added (as applicable, in case added or updated)
• Documentation changes have been listed (as applicable)
• Test suite output is added (as applicable)
• Pending actions have been added (optional)
• Any other additional notes have been added (optional)

Additional Information

• Appropriate label(s) have been added (ready for review should be added if the PR is ready to be reviewed)
• Assignee(s) and reviewer(s) have been added (optional)

---

Description:

Added docker and docker-compose files for containerization of application.

Related changes:

• Add short points about the different changes made within the files in this PR.

Screenshots:

Add any screenshots as required.

Query request and response:

• Add any query request body, cURL statement and response body for the made change or addition.

Documentation changes:

• Add a list of changes made to the API documents with brief descriptions.

Test suite output:

• Add the output of the status of different test cases in the testing suite.

Pending actions:

• Add list of any pending actions that have or would require to be done in this PR.

Additional notes:

• Add list of any additional notes you may want to convey in this PR.

Summary by CodeRabbit

• New Features

  • Added COMPOSE_PROJECT_NAME environment variable for better project identification.

• Improvements

  • Updated Dockerfile to use Node.js 20 for enhanced performance and security.
  • Enhanced docker-compose.yml to include configurations for MariaDB and Redis services.

• Bug Fixes

  • Modified response field from "id" to "jobId" in the createSummary mutation query for better clarity.

• Configuration Changes

  • Removed autoLoadEntities: true from TypeORM configuration to streamline database initialization.

[coderabbitai]

Walkthrough

The recent updates focus on enhancing the API application by improving its configuration and deployment setup. Key changes include the addition of a new environment variable, updating the Dockerfile to use Node.js 20, modifying a Postman collection response field, and refining the Docker Compose setup for better service management. Additionally, a configuration tweak was made to the TypeORM setup by removing the autoLoadEntities option.

Changes

Files	Change Summary
apps/api/.env.example	Added COMPOSE_PROJECT_NAME environment variable.
apps/api/Dockerfile	Updated to use Node.js 20, set working directory, copy files, set environment variables, install dependencies, build the NestJS app, expose port, and define the start command.
apps/api/Transcript Summarization.postman_collection.json	Modified response field from "id" to "jobId" in createSummary mutation query.
apps/api/docker-compose.yml	Introduced configurations for setting up services using Docker Compose, including API, MariaDB, and Redis.
apps/api/src/config/typeorm/configuration.ts	Removed autoLoadEntities: true from DataSource initialization.

🐰
In code we trust, with changes bright,
Docker and configs set just right.
With Node.js twenty, we now stand tall,
Summarizing transcripts, one and all.
Postman’s jobId, a tweak so small,
Together, we rise, and never fall.
🚀

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9709a41 and 66dbb11.

Files selected for processing (5)

• apps/api/.env.example (1 hunks)
• apps/api/Dockerfile (1 hunks)
• apps/api/Transcript Summarization.postman_collection.json (1 hunks)
• apps/api/docker-compose.yml (1 hunks)
• apps/api/src/config/typeorm/configuration.ts (1 hunks)

Files skipped from review due to trivial changes (4)

• apps/api/.env.example
• apps/api/Dockerfile
• apps/api/docker-compose.yml
• apps/api/src/config/typeorm/configuration.ts

Additional comments not posted (1)

apps/api/Transcript Summarization.postman_collection.json (1)

44-44: Ensure the change from "id" to "jobId" in the GraphQL mutation query aligns with the API's response structure.

Please confirm that the API's response structure has been updated to return "jobId" instead of "id" for the createSummary mutation. This change should be reflected in the API documentation and any related code.