laboratori-cloud/.planning/phases/05-lab-04-storage-s3/05-PLAN.md at main

Files

Luca Sacchi Ricciardi a021fe796b feat(lab-04): complete Phase 5 - Storage & S3 lab

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>

2026-04-03 15:25:46 +02:00

721 B

Raw Permalink Blame History

phase: 05-lab-04-storage-s3 plans: 1 (combined RED/GREEN for efficiency) type: execute wave: 0 requirements: LAB-04, INF-04, DOCT-01/02/03/04, PARA-01 must_haves: truths: - "Docker volumes named persist data across container restarts" - "MinIO provides S3-compatible API" - "INF-04 compliance: data survives container lifecycle" - "All Diátxis documents created" artifacts: - docker-compose.yml with MinIO + volumes - 6 test scripts - 11 documentation files objective: Create Lab 04 - Storage & S3 with Docker Volumes and MinIO. Key concepts: - Named volumes = EBS volumes - MinIO = S3 bucket - Data persistence across restarts Execute with TDD: tests first, then implementation.

721 B Raw Permalink Blame History

721 B

Raw Permalink Blame History