fix: mark portfolio_net as external to resolve compose label conflict

Docker Compose refused to adopt the existing portfolio_net network because
it lacked the expected com.docker.compose.network label (created outside
Compose). Mark it as external (matching the dev setup) and pre-create it
in the deployment workflow to ensure it always exists before compose up.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.gitea/workflows/production-deploy.yml

@@ -73,6 +73,9 @@ jobs:
           export DIRECTUS_URL="${{ vars.DIRECTUS_URL || 'https://cms.dk0.dev' }}"
           export DIRECTUS_STATIC_TOKEN="${{ secrets.DIRECTUS_STATIC_TOKEN || '' }}"
           
+          # Ensure the shared network exists before compose tries to use it
+          docker network create portfolio_net 2>/dev/null || true
+
           # Start new container with updated image (docker-compose will handle this)
           echo "🆕 Starting new production container..."
           echo "📝 Environment check: N8N_WEBHOOK_URL=${N8N_WEBHOOK_URL:-(not set)}"

docker-compose.production.yml

@@ -113,7 +113,6 @@ volumes:
 
 networks:
   portfolio_net:
-    name: portfolio_net
+    external: true
-    driver: bridge
   proxy:
     external: true