diff --git a/docs/contributing/setup.md b/docs/contributing/setup.md index 6d99fe6..fa31287 100644 --- a/docs/contributing/setup.md +++ b/docs/contributing/setup.md @@ -177,7 +177,7 @@ Create `docker-compose.dev.yml`: ```yaml services: - gemini-mcp: + zen-mcp: build: context: . dockerfile: Dockerfile.dev # If you have a dev Dockerfile diff --git a/docs/user-guides/configuration.md b/docs/user-guides/configuration.md index 3e8600f..d4ced88 100644 --- a/docs/user-guides/configuration.md +++ b/docs/user-guides/configuration.md @@ -139,7 +139,7 @@ Create `docker-compose.override.yml` for custom settings: ```yaml services: - gemini-mcp: + zen-mcp: environment: - LOG_LEVEL=DEBUG volumes: @@ -182,7 +182,7 @@ The container mounts your home directory as read-only. To restrict access: ```yaml # In docker-compose.override.yml services: - gemini-mcp: + zen-mcp: environment: - WORKSPACE_ROOT=/path/to/specific/project volumes: @@ -196,7 +196,7 @@ services: ```yaml # In docker-compose.override.yml services: - gemini-mcp: + zen-mcp: deploy: resources: limits: @@ -240,7 +240,7 @@ services: 3. **Redis Connection Issues** ```bash # Test Redis connectivity - docker exec -it gemini-mcp-redis redis-cli ping + docker exec -it zen-mcp-redis redis-cli ping ``` ### Debug Mode @@ -276,7 +276,7 @@ networks: driver: bridge services: - gemini-mcp: + zen-mcp: networks: - custom_network redis: diff --git a/docs/user-guides/installation.md b/docs/user-guides/installation.md index 198700b..89be2bd 100644 --- a/docs/user-guides/installation.md +++ b/docs/user-guides/installation.md @@ -190,14 +190,14 @@ cat > docker-compose.yml << 'EOF' services: redis: image: redis:7-alpine - container_name: gemini-mcp-redis + container_name: zen-mcp-redis restart: unless-stopped ports: - "6379:6379" volumes: - redis_data:/data - gemini-mcp: + zen-mcp: image: ghcr.io/beehiveinnovations/zen-mcp-server:latest container_name: zen-mcp-server restart: unless-stopped @@ -251,13 +251,13 @@ The Docker setup automatically mounts your home directory as `/workspace`. This # See if containers are running docker compose ps -# Should show both 'gemini-mcp-redis' and 'zen-mcp-server' as 'Up' +# Should show both 'zen-mcp-redis' and 'zen-mcp-server' as 'Up' ``` ### View Logs ```bash # Check MCP server logs -docker compose logs gemini-mcp -f +docker compose logs zen-mcp -f # Check Redis logs docker compose logs redis -f @@ -312,7 +312,7 @@ docker compose ps # Should show both containers as 'Up' # If not, check logs: -docker compose logs gemini-mcp +docker compose logs zen-mcp ``` ### "GEMINI_API_KEY environment variable is required" @@ -359,7 +359,7 @@ chmod +x setup-docker.sh The setup uses Docker Compose to orchestrate two services: -1. **Redis Container** (`gemini-mcp-redis`) +1. **Redis Container** (`zen-mcp-redis`) - Official Redis 7 Alpine image - Automatic data persistence with Docker volume - Available at `redis:6379` within Docker network diff --git a/docs/user-guides/troubleshooting.md b/docs/user-guides/troubleshooting.md index e0ef38a..8f51dae 100644 --- a/docs/user-guides/troubleshooting.md +++ b/docs/user-guides/troubleshooting.md @@ -90,7 +90,7 @@ docker compose ps docker compose ps redis # Test Redis connectivity -docker exec -it gemini-mcp-redis redis-cli ping +docker exec -it zen-mcp-redis redis-cli ping # Should return: PONG ``` @@ -139,7 +139,7 @@ docker stats ```yaml # In docker-compose.override.yml services: - gemini-mcp: + zen-mcp: deploy: resources: limits: