fix: update docker-compose retry policy to unless-stopped

[kshitij-k-osmosys]

API PR Checklist

Task Link

Osmosys Developers must include the Pinestem task link in the PR.

OSXT-1545

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 unit testing for the new feature added or updated to ensure the new features added are working as expected.
• I have added/updated test cases to the test suite as applicable.
• I have performed preliminary testing using the test suite to ensure that any existing features are not impacted and any new features are working as expected as a whole.
• I have added/updated the required api docs as applicable.
• I have added/updated the .env.example file with the required values 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/unit testing 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)

Note: Reviewer should ensure that the checklist and description have been populated and followed correctly, and the PR should be merged only after resolving all conversations and verifying that CI checks pass.

---

Description:

Update retry policy to unless-stopped for all docker-compose services

Summary by CodeRabbit

• Chores
  • Updated the restart policy for database and cache services to improve container management behavior.

[coderabbitai]

Walkthrough

The Docker Compose configuration was updated to change the restart policy for the MariaDB and Redis services from always to unless-stopped, altering how these containers restart in response to failures or manual stops.

Changes

File(s)	Change Summary
apps/api/docker-compose.yml	Changed restart policy for MariaDB and Redis from always to unless-stopped

Possibly related PRs

• build: add restart policy in docker compose file #76: Adjusts restart policies in the same docker-compose file, but for the API service instead of MariaDB and Redis.

Suggested labels

Ready for review

Suggested reviewers

• osm-vishnukyatannawar

Poem

A hop, a skip, a Docker tweak,
Restart rules now less oblique.
MariaDB and Redis, too,
Will nap when told, not always renew.
Compose files change, the code stays neat—
A bunny’s job is now 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: 0

🧹 Nitpick comments (1)

apps/api/docker-compose.yml (1)

34-34: DRY the identical restart policy with YAML anchors for easier future changes.

All services now share the same directive; you can de-duplicate:

x-restart-policy: &restart_policy
  restart: unless-stopped

services:
  transcript-summarizer-api:
    <<: *restart_policy
    ...
  transcript-summarizer-mariadb:
    <<: *restart_policy
    ...
  transcript-summarizer-redis:
    <<: *restart_policy
    ...

This keeps the policy changeable in one place.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 171bc8d and bcd225c.

📒 Files selected for processing (1)

• apps/api/docker-compose.yml (2 hunks)

🔇 Additional comments (2)

apps/api/docker-compose.yml (2)

20-20: Consistent restart policy – change meets objective.

restart: unless-stopped is now applied to MariaDB, matching the API service and fulfilling OSXT-1545.
No functional concerns.

---

18-20: ```shell
#!/bin/bash

Verify image tags in the docker-compose file

grep -R "image:.*latest" -n apps/api/docker-compose.yml || echo "No 'latest' tags found"

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->