From 717c363eb4c5447e65dd03efc18165c0975766cf Mon Sep 17 00:00:00 2001 From: Daniel Date: Thu, 10 Sep 2026 17:58:20 +0200 Subject: [PATCH] chore: the storage repos are named for what they hold MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ped-ai-storage held the personal assistant index, and nextcloud-mcp-server held ped-ai's clinical index and runs no MCP server at all — only etcd, MinIO and Milvus. The names said the opposite of the truth: ped-ai-storage -> personal-assistant-storage-milvus nextcloud-mcp-server -> clinical-storage-milvus Only the secret bind mounts here name those paths. Both compose files pin `name:`, so containers, networks and volumes keep their existing names and no data moves; that also means the container prefixes still read ped-ai-storage_*, which can only change by copying each volume. Verified: all three stacks' compose configs validate, ped-ai recreated with the new secret paths and reads them, and the storage stack still resolves its own containers from the renamed directory. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU --- docker-compose.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 84b263a4..00831664 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -37,8 +37,8 @@ services: volumes: - scribe-logs:/app/data/logs - clinical-assistant-mcp-data:/app/mcp-data:ro - - /home/danvics/docker/ped-ai-storage/secrets/images-access-key:/run/secrets/generated-images-access-key:ro - - /home/danvics/docker/ped-ai-storage/secrets/images-secret-key:/run/secrets/generated-images-secret-key:ro + - /home/danvics/docker/personal-assistant-storage-milvus/secrets/images-access-key:/run/secrets/generated-images-access-key:ro + - /home/danvics/docker/personal-assistant-storage-milvus/secrets/images-secret-key:/run/secrets/generated-images-secret-key:ro depends_on: postgres: condition: service_healthy