FEATURE REQUEST:Add Docker support to containerize Devr.AI for easy local setup

[Abhishek2005-ard]

Is your feature request related to a problem?

• Yes, it is related to a problem

Describe the feature you'd like

Currently, Devr.AI does not support Docker-based setup.
This makes local development and onboarding contributors harder,
as the environment must be configured manually.

Proposed solution:

• Add Dockerfile for frontend and backend (if applicable)
• Add docker-compose.yml to run the full stack
• Document Docker-based setup steps in README

Benefits:

• Faster onboarding for contributors
• Consistent development environment
• Easier testing and deployment

I would like to work on this issue if approved.

Record

• I agree to follow this project's Code of Conduct
• I want to work on implementing this feature

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[Abhishek2005-ard]

Thanks for reviewing this request.
I’m happy to start once it’s approved or assigned to me.

[tripcoded]

Hi maintainers

I’d like to work on this issue if it’s available.

I have prior experience setting up Docker-based development environments, including writing Dockerfiles for frontend/backends, configuring docker-compose.yml, and documenting setup steps for contributors.

I agree to follow the project’s Code of Conduct and will make sure the implementation aligns with the existing architecture and contribution guidelines.

Please let me know if I can take this up or if you’d like me to clarify the approach before starting.

Thanks!

[smokeyScraper]

Hey @Abhishek2005-ard
The current project already has a Docker setup for a majority of its functionalities in the backend ,except the GitHub MCP server. Can you please let me know what change do you propose?

[tripcoded]

Hey @smokeyScraper ,Thank you for the clarification.

I understand that the backend already has Docker support for most services, and that the GitHub MCP server is currently excluded.

I propose to:

1. Add a dedicated Dockerfile for the GitHub MCP server, aligned with the existing backend Docker patterns.
2. Update docker-compose.yml to include the MCP service with proper networking and environment variables.
3. Document the setup clearly in the README, explaining how to run the full stack including the MCP server.

This would make local setup fully containerized and improve onboarding consistency.
Please let me know if this approach sounds good or if you’d like any changes.

[FOX-KNIGHT]

I see that this project needs Docker support to streamline the setup process for new contributors. I would love to work on this!
I have experience containerizing full-stack applications and can implement a robust Docker setup that ensures consistency across development environments.
Implementation Plan
My goal is to create a lightweight and efficient containerized environment.

Technical Details (Click to expand)

• Dockerfiles: Implement multi-stage builds for both the Frontend and Backend to minimize image size and build time.
• Docker Compose: Create a docker-compose.yml to orchestrate services (Frontend, Backend, and Database if applicable) with hot-reloading enabled for a smooth development experience.
• Environment Management: Integrate .env file handling within the compose setup to ensure secure and flexible configuration.
• Optimization: Use .dockerignore to exclude node_modules and other unnecessary files from the build context.

I will follow this roadmap to complete the containerization:

• Container Configuration
  • Create optimized Dockerfile for the Backend.
  • Create optimized Dockerfile for the Frontend.
  • Create .dockerignore files for both.
• Orchestration
  • Create docker-compose.yml connecting all services (dev mode).
  • Configure volume mapping for hot-reloading.
  • Ensure networking and port forwarding are correctly set up.
• Documentation & Testing
  • Test the full startup flow on a fresh environment.
  • Update README.md with clear instructions on how to run the project using Docker (e.g., docker-compose up).
    I am ready to start immediately to help make onboarding easier for everyone!
    Please assign this to me.

[KumarADITHYA123]

Hi @smokeyScraper and @chandansgowda,

Thank you for the clarification. I completely understand the current architecture -
the backend already has Docker support for most services, with the GitHub MCP server
being the gap that needs to be addressed.

I'd like to take this issue forward with the following comprehensive approach:

1. GitHub MCP Server Containerization

• Create an optimized "Docker file" for the GitHub MCP server following the existing
  backend Docker patterns to maintain consistency
• Implement proper service configuration with environment variable management
• Ensure the container integrates seamlessly with the existing Docker network

2. Docker Compose Orchestration

• Update "docker-compose.yml" to include the GitHub MCP service
• Configure proper networking between services (backend, frontend, and MCP)
• Set up environment variable injection for MCP configuration
• Add volume mapping to support development-time hot-reloading
• Ensure port mappings align with the current architecture

3. Documentation & Testing

• Update README.md with clear instructions for running the full stack
  (e.g., docker-compose up for local development)
• Document any environment variables required for the MCP service
• Test the complete startup flow on a fresh environment to validate the setup

I have hands-on experience with Docker containerization, service orchestration,
and full-stack application deployment. I'm committed to ensuring this implementation
aligns with your project standards and architecture.

I'm ready to start immediately. Could you confirm if this approach meets the
project's requirements?

Thanks!

[KumarADITHYA123]

Hi @smokeyScraper and @chandansgowda,
I have successfully completed the Docker setup for the GitHub MCP Server.

As requested, I have focused only on containerizing the MCP service without modifying the existing backend infrastructure configuration.

Implementation Details

1. Standalone Docker Compose (docker-compose.yml)
   I created a root-level docker-compose.yml to orchestrate the github-mcp service.
   Why:
   This keeps the lightweight MCP environment decoupled from the heavier backend
   infrastructure (Weaviate/RabbitMQ), allowing for faster local testing.
   Networking:
   Maps internal port 8001 to host 5001.

2. Build Optimization (Crucial Fix)
   I modified the GitHub MCP Dockerfile to enforce a CPU-only installation for PyTorch.
   Context:
   The default PyTorch installation was attempting to pull ~2.5GB of Nvidia CUDA binaries,
   causing hash mismatches and build failures.
   Result:
   The build is now stable and significantly smaller, which is appropriate for this service.

3. Dependency Fix
   I added pydantic-settings to the requirements.txt.

Reason:
The app lication failed to start with an ImportError because settings.py relies on
BaseSettings, which was missing from the MCP environment.

✅ Verification
I have verified the setup on a fresh environment:
Build:
docker-compose up --build (Successful)

Health Check:

curl http://localhost:5001/health

Output: {"status": "healthy", "service": "github-mcp"}

I am ready to submit the PR. Please let me know if you used a different preferred naming convention for the service!