Skip to content

Conversation

HrishikeshUchake
Copy link
Contributor

@HrishikeshUchake HrishikeshUchake commented Jul 10, 2025

Closes #94

📝 Description

This PR introduces RabbitMQ as a first-class service in our local development Docker Compose setup. Developers can now spin up the full stack—including RabbitMQ and Weaviate—with a single:

docker-compose up -d

🔧 Changes Made

  • Version: '3.8': Bumped Compose file format to enable healthchecks.

  • Added rabbitmq service under services:

  • Uses the official rabbitmq:3-management image

  • Exposes AMQP (5672) and management UI (15672) ports

  • Pulls credentials from environment with sensible defaults (guest/guest)

  • Persists broker data in a named volume (rabbitmq_data)

  • Defines a Docker healthcheck using rabbitmq-diagnostics status

  • Named volume for RabbitMQ added alongside the existing weaviate_data volume

  • Consistent port quoting on Weaviate service for YAML style consistency

📷 Screenshots or Visual Changes (if applicable)

Screenshot 2025-07-10 at 3 13 38 AM

✅ Checklist

  • [✅] I have read the contributing guidelines.
  • [✅] I have added tests that prove my fix is effective or that my feature works.
  • [✅] I have added necessary documentation (if applicable).
  • [✅] Any dependent changes have been merged and published in downstream modules.

Summary by CodeRabbit

  • New Features

    • Added RabbitMQ as a new service in the application’s Docker setup, including a management UI and persistent storage.
  • Chores

    • Updated Docker configuration to support RabbitMQ service and its associated data volume.

Copy link
Contributor

coderabbitai bot commented Jul 10, 2025

Walkthrough

A RabbitMQ service has been added to the backend/docker-compose.yml file. This includes a service configuration using the rabbitmq:3-management image, port mappings for AMQP and management UI, environment variable support for credentials, persistent storage via a named volume, a health check, and a new volume declaration.

Changes

File(s) Change Summary
backend/docker-compose.yml Added rabbitmq service with image, ports, env vars, health check, persistent volume, and new rabbitmq_data volume.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant DockerCompose
    participant RabbitMQ
    participant Weaviate

    Developer->>DockerCompose: docker-compose up
    DockerCompose->>RabbitMQ: Start container (rabbitmq:3-management)
    DockerCompose->>Weaviate: Start container (existing)
    RabbitMQ->>Developer: Expose AMQP (5672), Management UI (15672)
    RabbitMQ->>DockerCompose: Health check (periodic)
Loading

Assessment against linked issues

Objective Addressed Explanation
Add RabbitMQ service to docker-compose.yml (#94)
Allow RabbitMQ to be started/stopped with other services via docker-compose (#94)
Expose RabbitMQ ports 5672 (AMQP) and 15672 (management UI) (#94)
Support for persistent storage for RabbitMQ (#94)
Allow RabbitMQ credentials to be set via environment variables (#94)

Poem

A hop, a skip, a Docker spin,
Now RabbitMQ is tucked right in!
Compose it up, no need to chase,
AMQP and UI—one rabbit's embrace.
With queues and carrots, we now deploy,
A burrow of messages, oh what joy!
🐇💌


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
🪧 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (3)
backend/docker-compose.yml (3)

26-28: Avoid hard-coding container_name unless strictly required.

Pinning container_name: rabbitmq prevents multiple check-outs of the stack on the same host and breaks docker compose down --volumes name scoping. Unless external scripts rely on the name, consider removing it.


37-42: Make the health-check quieter & faster.

rabbitmq-diagnostics status is verbose and exits 0 even when some subsystems are degraded. The typical pattern is:

-      test: ["CMD", "rabbitmq-diagnostics", "status"]
+      test: ["CMD", "rabbitmq-diagnostics", "-q", "ping"]

-q ping is faster (<1 s) and returns non-zero when the node is not running.


44-47: Volume declaration indentation

The new rabbitmq_data: key should be flush with weaviate_data:—otherwise older YAML parsers may interpret it as a child of the previous key.

 volumes:
   weaviate_data:
-  rabbitmq_data:
+  rabbitmq_data:

(Only whitespace changes.)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8700e48 and ebecc14.

📒 Files selected for processing (1)
  • backend/docker-compose.yml (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings
Learnt from: smokeyScraper
PR: AOSSIE-Org/Devr.AI#72
File: backend/app/core/orchestration/queue_manager.py:48-66
Timestamp: 2025-06-08T13:27:45.522Z
Learning: The queue manager implementation in backend/app/core/orchestration/queue_manager.py is temporary and will be replaced with RabbitMQ in the future.
🔇 Additional comments (2)
backend/docker-compose.yml (2)

1-2: Specify the Compose file version explicitly.

The PR description states that the file was upgraded to version 3.8, but the version: "3.8" key is missing. While modern docker compose CLIs infer the latest spec, older docker-compose binaries will fail to parse health-checks unless the version is declared.

---
+version: "3.8"
 services:

28-33: Expose credentials only when necessary.

guest/guest is fine for local dev, but the ports are bound to the host. Anyone on the developer’s network can reach 15672 and 5672.
Options:

  1. Bind to localhost only:
-      - '5672:5672'
-      - '15672:15672'
+      - '127.0.0.1:5672:5672'
+      - '127.0.0.1:15672:15672'
  1. Or require env-file overrides for non-default creds.

@smokeyScraper smokeyScraper merged commit 1353f35 into AOSSIE-Org:main Jul 10, 2025
1 check passed
@smokeyScraper
Copy link
Contributor

Merged! @HrishikeshUchake,
cheers!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FEATURE REQUEST: Integrate RabbitMQ Service into Docker Compose

2 participants