fix: run prisma migrations on Railway startup instead of GitHub Actions (#121)

GitHub Actions can't reach Supabase direct DB connection (firewalled).
Move `prisma migrate deploy` into start:prod so it runs on Railway
where the DB is already reachable.

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: willwearing

.github/workflows/ci-deploy.yml

@@ -188,22 +188,6 @@ jobs:
     steps:
       - uses: actions/checkout@v5
 
-      - uses: oven-sh/setup-bun@v2
-        with:
-          bun-version: "1.3.6"
-
-      - name: Install dependencies
-        run: bun install
-
-      - name: Generate Prisma client
-        run: cd backend && bun x prisma generate
-
-      - name: Run production migrations
-        run: cd backend && bun x prisma migrate deploy
-        env:
-          DATABASE_URL: ${{ secrets.DATABASE_URL }}
-          DIRECT_URL: ${{ secrets.DIRECT_URL }}
-
       - name: Install Railway CLI
         run: npm install -g @railway/cli
 

backend/package.json

@@ -6,7 +6,7 @@
     "build": "prisma generate && nest build",
     "dev": "bun x nest build && bun x nest start --watch",
     "start": "nest start",
-    "start:prod": "TS_NODE_PROJECT=tsconfig.runtime.json node -r tsconfig-paths/register dist/main.js",
+    "start:prod": "prisma migrate deploy && TS_NODE_PROJECT=tsconfig.runtime.json node -r tsconfig-paths/register dist/main.js",
     "test": "jest",
     "test:watch": "jest --watch",
     "lint": "eslint --config eslint.config.mjs \"{src,prisma}/**/*.ts\" --fix"