fix(docker): use start.sh script instead of railway.toml startCommand

Railway was ignoring startCommand, so move migration + server start
into a shell script baked into the Docker image.

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

Author: junzero741

apps/backend/Dockerfile

@@ -47,6 +47,9 @@ COPY --from=builder /app/apps/backend/prisma ./prisma
 # Create prisma.config.js for production (reads DATABASE_URL from env)
 RUN echo 'const { defineConfig } = require("prisma/config"); module.exports = defineConfig({ schema: "prisma/schema.prisma", migrations: { path: "prisma/migrations" }, datasource: { url: process.env.DATABASE_URL } });' > prisma.config.js
 
+COPY --from=builder /app/apps/backend/start.sh ./
+RUN chmod +x start.sh
+
 EXPOSE 4000
 
-CMD ["node", "main.js"]
+CMD ["./start.sh"]

apps/backend/start.sh

@@ -0,0 +1,6 @@
+#!/bin/sh
+set -e
+echo "Running migrations..."
+npx prisma migrate deploy
+echo "Starting server..."
+exec node main.js

railway.toml

@@ -2,5 +2,4 @@
 dockerfilePath = "apps/backend/Dockerfile"
 
 [deploy]
-startCommand = "npx prisma migrate deploy; echo 'MIGRATE DONE'; node main.js; echo \"NODE EXIT: $?\""
 restartPolicyType = "ON_FAILURE"