docker-compose.yml

services:
  wiki:
    build: .
    ports: ["8080:8080"]
    environment:
      WIKI_API_KEY: ${WIKI_API_KEY:?set WIKI_API_KEY in .env}
    volumes:
      - wiki-data:/vault
    restart: unless-stopped

volumes:
  wiki-data:
feat(server): run a vault as a Dockerized HTTP + MCP memory service (#185) Everything else here is local: skills on your machine, a vault on your disk. This puts a vault behind a URL so an agent elsewhere can search and write it. One container, one vault, one API key. The vault stays plain markdown on a mounted volume, so Obsidian still opens it. The container does no LLM work -- search and packing delegate to the existing graphrag/context_pack modules, and the caller's agent does the thinking. - obsidian_wiki/server.py: four vault functions, five REST routes and four MCP tools as transport over them. Auth is one bearer key; the process refuses to start without WIKI_API_KEY unless WIKI_ALLOW_ANONYMOUS=1. Every path is resolved inside the vault or refused. - Dockerfile, docker-compose.yml, .dockerignore, and a ghcr push on v* tags. - New [server] extra; the core wheel stays dependency-free. - docs/deployment.md, plus the WIKI_* vars in configuration.md and .env.example. Requires mcp>=2.0: 2.0 renamed FastMCP to MCPServer, and session_manager only exists once streamable_http_app() has been called -- a mounted sub-app's own lifespan is ignored, so it is wired into the FastAPI lifespan by hand. 2026-08-21 14:37:37 -07:00			`services:`
			`wiki:`
			`build: .`
			`ports: ["8080:8080"]`
			`environment:`
			`WIKI_API_KEY: ${WIKI_API_KEY:?set WIKI_API_KEY in .env}`
			`volumes:`
			`- wiki-data:/vault`
			`restart: unless-stopped`

			`volumes:`
			`wiki-data:`