fix(docker): keep server Postgres on ./data/postgres, move Windows volume to an override

751cac7 switched the base compose file to an external named volume
(bellsystems-postgres-data) to dodge a WSL2/Docker Desktop bind-mount bug.
That volume only exists on the Windows dev machine: on the VPS, where the
push auto-deploys via deploy-host.sh, `docker compose up` would fail on the
missing external volume (or, if created, start Postgres on an empty
database while the real data sat unused in ./data/postgres).

The base file goes back to the ./data/postgres bind mount the server has
always used (Linux has no such bug). The named volume now lives in
docker-compose.override.yml, which Compose loads automatically, is
gitignored, and is created from docker-compose.override.example.yml on
Windows machines only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This commit is contained in:

bonamin

2026-09-30 16:45:58 +03:00

co-authored by

Claude Opus 5.5

parent f1a7c5a7ca

commit 18705aaefb

3 changed files with 25 additions and 16 deletions

.gitignore

+3 -1

View File

@@ -40,4 +40,6 @@ Thumbs.db
 .project-vesper-plan.md
 # claude
 .claude/
 .claude/
 # Per-machine compose overrides (e.g. Windows Postgres volume)
 docker-compose.override.yml