Switch PostgreSQL and MinIO from bind mounts to named volumes for production #131
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Priority: medium — must be resolved before production deployment
docker-compose.ymluses bind mounts for persistent data (lines 12 and 33):Bind mounts are fine for local development but wrong for production. Host path permissions or an accidental
docker compose down -vcan result in data loss. Named volumes are Docker-managed and more resilient.What to do
In the production compose file/overlay, replace bind mounts with named volumes:
The development
docker-compose.ymlcan keep the bind mounts for easy local data inspection.