a021fe796b
Phase Plan: - 05-PLAN.md: Combined execution plan for efficiency - 05-RESEARCH.md: Domain research on volumes and MinIO Test Scripts (4): - 01-volumes-test.sh: Volume persistence verification - 02-minio-test.sh: MinIO S3 API testing - 03-persistence-test.sh: Database persistence verification - 99-final-verification.sh: End-to-end verification Documentation (6 files): Tutorial: Docker volumes, MinIO S3 How-to: Manage volumes Reference: Volume syntax Explanation: Storage↔S3 parallels Infrastructure: - docker-compose.yml: MinIO S3 + PostgreSQL + test container - Named volumes: minio-data, db-data, test-data (INF-04 compliant) Key concepts: - Named volumes = EBS volumes - MinIO = S3 bucket (100% API compatible) - Data persistence across container lifecycle Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
537 B
537 B
Phase 5 Research - Storage & S3
Docker Volumes = EBS Volumes
| Docker | AWS EBS |
|---|---|
| docker volume create | aws ec2 create-volume |
| Named volume | EBS volume ID |
| Mount to /data | Attach to /dev/sdf |
| Data survives restart | Data persists independently |
MinIO = S3
MinIO features:
- 100% S3 API compatible
- Local development
- Same SDKs (boto3, aws cli)
- Buckets and objects
Key Commands
docker volume ls docker volume inspect mc ls (MinIO client) aws s3 --endpoint-url http://localhost:9000