-
Notifications
You must be signed in to change notification settings - Fork 0
Volume Management
Griffen Fargo edited this page Apr 10, 2026
·
1 revision
strut provides dynamic volume management driven by volume.conf in each stack.
strut my-stack volumes status --env prod # Show volume status
strut my-stack volumes init --env prod # Initialize volumes
strut my-stack volumes config --env prod # Show volume configurationDefine volume mappings in stacks/<stack>/volume.conf:
# volume_name:host_path:container_path:owner_uid:owner_gid
postgres_data:/var/lib/postgresql/data:/var/lib/postgresql/data:999:999
uploads:/app/uploads:/app/uploads:1000:1000
redis_data:/data:/data:999:999strut my-stack volumes init --env prodCreates host directories, sets ownership, and ensures volumes are ready before deployment.
When migrating from an existing setup, reference existing Docker volumes:
# In docker-compose.yml
volumes:
postgres-data:
external: true
name: existing_postgres_data# Stop containers only
strut my-stack stop --env prod
# Stop and remove volumes (⚠️ data loss)
strut my-stack stop --env prod --volumesstrut · v0.1.0 · Report an Issue
Getting Started
Core Concepts
Operations
- Deployment
- Remote Host Setup
- Blue-Green Deploy
- Deploy Rollback
- Database Backups
- Stack Groups
- Lifecycle Hooks
- Notifications
- Key Rotation
- Drift Detection
- Domain and SSL
- Monitoring
- Volume Management
Advanced
- Security Posture
- VPS Audit and Migration
- Stack Validation
- Data Anonymization
- Debugging
- Local Development
Extending
Contributing