Simplify Docker Compose to single-file architecture
- Convert multi-file overlay approach to single docker-compose.yml - Use environment variables for dev/production differences - Remove complex network configuration conflicts - Align with framework principles: simplicity over complexity - Production config via .env.production file Benefits: - No more network subnet conflicts - Single source of truth - Framework-compliant architecture - Easier maintenance and debugging Related: #19 Docker network conflict resolution
This commit is contained in:
@@ -182,21 +182,21 @@ networks:
|
||||
ipam:
|
||||
driver: default
|
||||
config:
|
||||
- subnet: 172.20.0.0/24
|
||||
- subnet: 172.24.0.0/24
|
||||
backend:
|
||||
driver: bridge
|
||||
internal: true # Backend network is internal-only
|
||||
ipam:
|
||||
driver: default
|
||||
config:
|
||||
- subnet: 172.21.0.0/24
|
||||
- subnet: 172.25.0.0/24
|
||||
cache:
|
||||
driver: bridge
|
||||
internal: true # Cache network is internal-only
|
||||
ipam:
|
||||
driver: default
|
||||
config:
|
||||
- subnet: 172.22.0.0/24
|
||||
- subnet: 172.26.0.0/24
|
||||
|
||||
volumes:
|
||||
redis_data:
|
||||
|
||||
Reference in New Issue
Block a user