Skip to content

Remove self-managed MongoDB service from production - #54

Open
gekinci wants to merge 2 commits into
mainfrom
vm-mongo-service
Open

Remove self-managed MongoDB service from production#54
gekinci wants to merge 2 commits into
mainfrom
vm-mongo-service

Conversation

@gekinci

@gekinci gekinci commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Since production now uses the MongoDB service provided by the VM, the production Docker Compose stack should no longer start or manage its own MongoDB container. But CI still needs an isolated MongoDB service for production smoke tests.

Changes:

  • Removed mongodb service from docker-compose.yml and climateclaw service dependency on the MongoDB container.
  • Added docker-compose.ci.yml with a CI-only MongoDB service.
  • Updated the CI production smoke test to run with both docker-compose.yml and docker-compose.ci.yml.

@gekinci gekinci self-assigned this Aug 20, 2026
@gekinci

gekinci commented Aug 21, 2026

Copy link
Copy Markdown
Collaborator Author

@antarcticrainforest can you take a look at this. It is a mini PR.

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.

1 participant