joakimp
b9c08c3dbb
Install mempalace via pip in the Dockerfile. Provides 29 MCP tools for semantic search over conversation history, knowledge graph queries, agent diaries, and wing/room/drawer management. Everything runs locally — no API keys, no data egress. Integration: - Dockerfile: pip install mempalace (with --break-system-packages for Debian trixie PEP 668 compliance) - entrypoint-user.sh: auto-initializes palace for /workspace on first run (idempotent, skips if palace exists) - entrypoint.sh: adds ~/.mempalace to the volume ownership-fix loop - docker-compose.yml + shared: optional devbox-palace named volume at ~/.mempalace (commented out by default — user opts in) Users configure MCP integration by adding a mempalace server entry to their opencode.json. No wrapper plugin needed — the upstream Python MCP server is used directly. Docs updated: README.md (new MemPalace section with setup, MCP config, usage examples, storage details), DOCKER_HUB.md (data storage table + tools list), CHANGELOG.md (unreleased entry).
113 lines
4.3 KiB
YAML
113 lines
4.3 KiB
YAML
# opencode-devbox docker-compose
|
|
#
|
|
# Usage:
|
|
# cp .env.example .env # configure your provider and keys
|
|
# docker compose up -d
|
|
# docker compose exec -u developer devbox opencode
|
|
#
|
|
# Or for interactive one-shot:
|
|
# docker compose run --rm devbox
|
|
|
|
# Pin the project name so named volumes survive directory renames.
|
|
# Without this, Docker Compose derives the project name from the
|
|
# directory basename — renaming the dir orphans all existing volumes.
|
|
name: opencode-devbox
|
|
|
|
services:
|
|
devbox:
|
|
image: joakimp/opencode-devbox:latest
|
|
# For multi-agent orchestration, use the omos variant instead:
|
|
# image: joakimp/opencode-devbox:latest-omos
|
|
#
|
|
# To build from source instead of pulling from Docker Hub, uncomment:
|
|
# build:
|
|
# context: .
|
|
# args:
|
|
# INSTALL_PYTHON: "false"
|
|
# INSTALL_GO: "false"
|
|
# INSTALL_OMOS: "false"
|
|
container_name: opencode-devbox
|
|
stdin_open: true
|
|
tty: true
|
|
env_file:
|
|
- .env
|
|
environment:
|
|
- TERM=xterm-256color
|
|
volumes:
|
|
# Host workspace — mount your project here
|
|
- ${WORKSPACE_PATH:-.}:/workspace
|
|
|
|
# SSH keys (read-only) — for git push/pull
|
|
- ${SSH_KEY_PATH:-~/.ssh}:/home/developer/.ssh:ro
|
|
|
|
# Optional: mount opencode config directory (persists config changes across restarts)
|
|
# Includes opencode.json, oh-my-opencode-slim.json, skills, etc.
|
|
# When mounted, OPENCODE_PROVIDER auto-config is skipped if opencode.json exists.
|
|
# - ~/.config/opencode:/home/developer/.config/opencode
|
|
|
|
# Optional: mount opencode agent skills from host
|
|
# - ~/.agents/skills:/home/developer/.agents/skills:ro
|
|
|
|
# Optional: mount neovim config from host (plugins auto-install on first start)
|
|
# - ~/.config/nvim:/home/developer/.config/nvim:ro
|
|
|
|
# Optional: persist opencode data (auth, memory, etc.)
|
|
- devbox-data:/home/developer/.local/share/opencode
|
|
|
|
# Optional: persist opencode TUI settings (theme, toggles, etc.)
|
|
- devbox-state:/home/developer/.local/state/opencode
|
|
|
|
# Persist bash history across container recreations.
|
|
# Without this, ~/.bash_history is lost on 'docker compose up --force-recreate'.
|
|
- devbox-shell-history:/home/developer/.cache/bash
|
|
|
|
# Persist zoxide directory history ('z <fragment>' to jump).
|
|
- devbox-zoxide:/home/developer/.local/share/zoxide
|
|
|
|
# Optional: override baked shell defaults with your host's rc files.
|
|
# The image ships sensible defaults (history tuning, prefix-search on
|
|
# Up/Down arrows, fzf/zoxide integration). Uncomment to use your own:
|
|
#
|
|
# NOTE: Single-file bind-mounts break when editors use atomic save
|
|
# (vim, VS Code, sed -i write a temp file then rename() over the
|
|
# original, creating a new inode the container never sees). This is a
|
|
# kernel limitation, not Docker-specific. If host edits stop appearing
|
|
# in the container, mount the parent directory instead — see the
|
|
# "Shell defaults" section in README.md.
|
|
# - ~/.bash_aliases:/home/developer/.bash_aliases:ro
|
|
# - ~/.inputrc:/home/developer/.inputrc:ro
|
|
|
|
# Optional: persist uv data (Python installs, tool installs)
|
|
# Without this, 'uv python install' must be re-run after container removal.
|
|
- devbox-uv:/home/developer/.local/share/uv
|
|
|
|
# Optional: persist Rust toolchains and cargo data
|
|
# Without this, 'rustup-init' must be re-run after container removal.
|
|
# - devbox-rustup:/home/developer/.rustup
|
|
# - devbox-cargo:/home/developer/.cargo
|
|
|
|
# Optional: persist VS Code server and extensions across container recreations
|
|
# - devbox-vscode:/home/developer/.vscode-server
|
|
|
|
# Persist neovim plugin/Mason data (avoids re-downloading on every recreate)
|
|
- devbox-nvim-data:/home/developer/.local/share/nvim
|
|
|
|
# Optional: persist MemPalace data (conversation memory, knowledge graph,
|
|
# embeddings). Without this, palace data is lost on container recreation.
|
|
# - devbox-palace:/home/developer/.mempalace
|
|
|
|
# Optional: AWS credentials/SSO config (not read-only — SSO writes token cache)
|
|
# - ~/.aws:/home/developer/.aws
|
|
|
|
volumes:
|
|
devbox-data:
|
|
devbox-state:
|
|
devbox-shell-history:
|
|
devbox-zoxide:
|
|
devbox-nvim-data:
|
|
devbox-uv:
|
|
# devbox-palace:
|
|
# devbox-rustup:
|
|
# devbox-cargo:
|
|
# devbox-vscode:
|