feat: add Codebase Memory MCP container sidecar - #7
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2b34705261
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| CBM_CACHE_DIR: /var/lib/codebase-memory | ||
| volumes: | ||
| - ${MCP_WORKSPACE:-./workspace}:/workspace:ro | ||
| - ${CBM_DATA:-./codebase-memory}:/var/lib/codebase-memory |
There was a problem hiding this comment.
Ignore the default Codebase Memory data directory
When CBM_DATA is unset, starting this profile creates ./codebase-memory inside the repository. This path is excluded by neither .gitignore nor .dockerignore, so the generated graph/cache appears as untracked files and is included in subsequent Docker build contexts, which can become substantial after indexing. Add the default persistence directory to both ignore files or place it outside the build context.
Useful? React with 👍 / 👎.
Adds an optional
codebase-memoryDocker Compose profile using DeusData/codebase-memory-mcp v0.10.8, bridged from stdio to stateful Streamable HTTP with Supergateway 3.2.0. The sidecar mounts the shared workspace read-only, persists its graph/cache separately, binds port 9750 to localhost only, supports amd64/arm64, verifies upstream release checksums, documents configuration, and adds a real MCP initialize + tools/list container smoke test.