fix: use robust start.sh script for deployment

apps/whatsapp-worker/Dockerfile

@@ -28,8 +28,9 @@ ENV NODE_OPTIONS="--dns-result-order=ipv4first"
 # Expose the API port (Railway uses PORT env var, default 3001)
 EXPOSE 3001
 
-# ─── Combined startup ─────────────────────────────────────────────────────────
-# db:push is best-effort — failure must NOT block the API or worker.
-# API (webhook + REST) and worker (BullMQ) start in parallel.
-CMD ["sh", "-c", "echo '[CMD] Starting Database Push...' && (pnpm --filter @repo/database db:push || echo '[CMD] db:push failed, continuing...'); echo '[CMD] Starting API Server...' && pnpm --filter api start & sleep 5 && echo '[CMD] Starting WhatsApp Worker...' && pnpm --filter whatsapp-worker start & wait"]
+# Make startup script executable
+RUN chmod +x ./start.sh
+
+# Start services using the robust script
+CMD ["./start.sh"]
 

start.sh

@@ -0,0 +1,30 @@
+#!/bin/sh
+
+echo "🚀 Starting EdTech Platform..."
+
+# 1. Sync Database (Non-blocking)
+echo "[DB] Syncing database schema..."
+pnpm --filter @repo/database db:push || echo "[DB] db:push failed, continuing anyway..."
+
+# 2. Start API Server
+echo "[API] Starting API Gateway on port ${PORT:-8080}..."
+# Using direct path to avoid pnpm overhead and potential filter issues
+npx tsx apps/api/src/index.ts &
+API_PID=$!
+
+# 3. Wait a bit for API to initialize
+sleep 5
+
+# 4. Start WhatsApp Worker
+echo "[WORKER] Starting WhatsApp Worker on internal port 8081..."
+npx tsx apps/whatsapp-worker/src/index.ts &
+WORKER_PID=$!
+
+echo "[SYSTEM] Both services are starting. Monitoring processes..."
+
+# 5. Wait and handle exits
+wait -n $API_PID $WORKER_PID
+
+echo "[SYSTEM] One of the services exited. Shutting down..."
+kill $API_PID $WORKER_PID 2>/dev/null
+exit 1