chore: the storage repos are named for what they hold
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dv6sqaY6Vq3ChZHMem3cnU
This commit is contained in:
parent
596fd897f6
commit
717c363eb4
1 changed files with 2 additions and 2 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in a new issue