feat: enhance network isolation and environment variable documentation for Coolify deployments

README_Network_Isolation_Dynamic.md

@@ -0,0 +1,106 @@
+# Network Isolation Setup for LearnHouse Deployments
+
+This setup provides complete network isolation between your DEV and LIVE LearnHouse deployments using a single dynamic Docker Compose file and environment variables.
+
+## Single Dynamic Compose File
+
+- `docker-compose-coolify.yml` - Works for both DEV and LIVE deployments using environment variables
+
+## Key Environment Variables for Isolation
+
+### Required for Network Isolation
+- `DEPLOYMENT_NAME` - Unique identifier for each deployment (e.g., "dev", "live", "staging")
+- `LEARNHOUSE_DOMAIN` - Domain for this specific deployment
+- `LEARNHOUSE_COOKIE_DOMAIN` - Exact domain for cookies (should match LEARNHOUSE_DOMAIN)
+
+### How It Works
+The compose file uses `${DEPLOYMENT_NAME:-learnhouse}` patterns to create:
+- **Networks**: `{DEPLOYMENT_NAME}-network` (e.g., `dev-network`, `live-network`)
+- **Traefik Routes**: `{DEPLOYMENT_NAME}` router names
+- **Volumes**: Handled automatically by Coolify (each deployment gets isolated volumes)
+
+## Coolify Deployment Instructions
+
+### For DEV Environment (adr-lms.whitex.cloud)
+
+1. In Coolify, create a new resource/service
+2. Use the standard `docker-compose-coolify.yml` file
+3. Set these **key environment variables**:
+   ```
+   DEPLOYMENT_NAME=dev
+   LEARNHOUSE_DOMAIN=adr-lms.whitex.cloud
+   LEARNHOUSE_COOKIE_DOMAIN=adr-lms.whitex.cloud
+   NEXTAUTH_URL=https://adr-lms.whitex.cloud
+   # ... your other DEV environment variables
+   ```
+
+### For LIVE Environment (edu.adradviser.ro)
+
+1. In Coolify, create a new resource/service  
+2. Use the same `docker-compose-coolify.yml` file
+3. Set these **key environment variables**:
+   ```
+   DEPLOYMENT_NAME=live
+   LEARNHOUSE_DOMAIN=edu.adradviser.ro
+   LEARNHOUSE_COOKIE_DOMAIN=edu.adradviser.ro
+   NEXTAUTH_URL=https://edu.adradviser.ro
+   # ... your other LIVE environment variables
+   ```
+
+## Network Isolation Results
+
+With `DEPLOYMENT_NAME=dev`:
+- Network: `dev-network`
+- Traefik Router: `dev`
+- Volumes: Automatically isolated by Coolify
+
+With `DEPLOYMENT_NAME=live`:
+- Network: `live-network`  
+- Traefik Router: `live`
+- Volumes: Automatically isolated by Coolify
+
+## Benefits
+
+✅ **Single File Maintenance**: One compose file for all environments
+✅ **Complete Backend Isolation**: Different networks prevent cross-communication
+✅ **Separate Data Storage**: Coolify automatically isolates volumes per deployment
+✅ **Unique Traefik Routes**: No router name conflicts
+✅ **Exact Cookie Domain Matching**: Prevents any cookie sharing
+✅ **Environment Flexibility**: Easy to add new environments (staging, testing, etc.)
+
+## Verification
+
+After deployment, verify isolation:
+
+1. **Check Docker networks**:
+   ```bash
+   docker network ls | grep -E "(dev|live)-network"
+   ```
+
+2. **Verify volumes** (Coolify handles this automatically):
+   ```bash
+   docker volume ls | grep your-project-name
+   ```
+
+3. **Test cookie domains** in browser DevTools:
+   - DEV cookies: domain `adr-lms.whitex.cloud`
+   - LIVE cookies: domain `edu.adradviser.ro`
+
+## Adding New Environments
+
+To add a staging environment:
+```
+DEPLOYMENT_NAME=staging
+LEARNHOUSE_DOMAIN=staging.example.com
+LEARNHOUSE_COOKIE_DOMAIN=staging.example.com
+```
+
+This automatically creates `staging-network` and Coolify handles volume isolation.
+
+## Troubleshooting
+
+If you experience cookie mixing:
+1. **Verify DEPLOYMENT_NAME** is set differently for each deployment
+2. **Check cookie domains** match exactly in browser DevTools
+3. **Clear browser data** for both domains
+4. **Confirm network isolation** using the verification commands above