chore: split Coolify compose configuration

CLAUDE.md

@@ -13,7 +13,7 @@ npm run start    # Start production server
 npm run lint     # ESLint (eslint-config-next/core-web-vitals + typescript)
 ```
 
-Docker deployment: port 8019, `docker-compose up` with env supplied by the deployment platform or shell, external network `sinobridge`.
+Docker deployment: port 8019. Default `docker-compose.yml` uses `.env.production` and external network `sinobridge`; Coolify uses `docker-compose.coolify.yml` with runtime env from Coolify and external network `coolify`.
 
 ## Architecture
 

README.md

@@ -74,7 +74,9 @@ The included Dockerfile builds a standalone Next.js output and starts `server.js
 docker compose up -d --build
 ```
 
-Set the required environment variables through your deployment platform or shell before starting Compose. The included `docker-compose.yml` expects an external Docker network named `sinobridge`.
+The default `docker-compose.yml` expects `.env.production` and an external Docker network named `sinobridge`.
+
+For Coolify deployments, use `docker-compose.coolify.yml`. It expects runtime environment variables from Coolify and an external Docker network named `coolify`.
 
 ## Operational Notes
 

docker-compose.coolify.yml

@@ -0,0 +1,15 @@
+services:
+  analytics:
+    build: .
+    container_name: new-api-analytics
+    restart: unless-stopped
+    ports:
+      - "8019:8019"
+    environment:
+      - SERVICE_URL_ANALYTICS_8019
+    networks:
+      - coolify
+
+networks:
+  coolify:
+    external: true

docker-compose.yml

@@ -5,8 +5,8 @@ services:
     restart: unless-stopped
     ports:
       - "8019:8019"
-    environment:
-      - SERVICE_URL_ANALYTICS_8019
+    env_file:
+      - .env.production
     networks:
       - sinobridge