ci: use Railway API token for deploy auth

Author: khangtrannn

.github/workflows/deploy.yml

@@ -23,11 +23,11 @@ jobs:
 
       - name: Verify Railway secrets
         run: |
-          test -n "$RAILWAY_TOKEN" || (echo "Missing RAILWAY_TOKEN GitHub repository secret" && exit 1)
+          test -n "$RAILWAY_API_TOKEN" || (echo "Missing RAILWAY_API_TOKEN GitHub repository secret" && exit 1)
           test -n "$RAILWAY_PROJECT_ID" || (echo "Missing RAILWAY_PROJECT_ID GitHub repository secret" && exit 1)
           test -n "$RAILWAY_SERVICE_ID" || (echo "Missing RAILWAY_SERVICE_ID GitHub repository secret" && exit 1)
         env:
-          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
+          RAILWAY_API_TOKEN: ${{ secrets.RAILWAY_API_TOKEN }}
           RAILWAY_PROJECT_ID: ${{ secrets.RAILWAY_PROJECT_ID }}
           RAILWAY_SERVICE_ID: ${{ secrets.RAILWAY_SERVICE_ID }}
 
@@ -40,7 +40,7 @@ jobs:
       - name: Deploy to Railway
         run: railway up --project "$RAILWAY_PROJECT_ID" --service "$RAILWAY_SERVICE_ID" --environment production --ci
         env:
-          RAILWAY_TOKEN: ${{ secrets.RAILWAY_TOKEN }}
+          RAILWAY_API_TOKEN: ${{ secrets.RAILWAY_API_TOKEN }}
           RAILWAY_PROJECT_ID: ${{ secrets.RAILWAY_PROJECT_ID }}
           RAILWAY_SERVICE_ID: ${{ secrets.RAILWAY_SERVICE_ID }}
 

README.md

@@ -187,7 +187,7 @@ flowchart TD
 - **Backend → Railway** - `railway up` is run **from the repo root**, not `backend/`, because the Railway service is already configured with `Root Directory=/backend`; uploading the full repo lets Railway apply that configured root itself. Railway's own pre-deploy step (`npm run migration:run:prod`) handles production migrations - CI's `migration:run` is only there to validate migrations apply cleanly, not to apply them to production.
 - **Frontend → Cloudflare Pages** - built with `VITE_API_BASE_URL` pointed at production, then pushed with **Direct Upload** (`npx wrangler pages deploy dist --project-name simple-invoice --branch main`). This deliberately does **not** use Cloudflare's Git integration or `wrangler deploy` (that command targets Workers, not Pages).
 
-Required GitHub repository secrets: `CLOUDFLARE_ACCOUNT_ID`, `CLOUDFLARE_API_TOKEN`, `RAILWAY_TOKEN`, `RAILWAY_PROJECT_ID`, `RAILWAY_SERVICE_ID`. If any of these are missing or empty, `deploy.yml` fails before starting the deploy and prints the missing secret name.
+Required GitHub repository secrets: `CLOUDFLARE_ACCOUNT_ID`, `CLOUDFLARE_API_TOKEN`, `RAILWAY_API_TOKEN`, `RAILWAY_PROJECT_ID`, `RAILWAY_SERVICE_ID`. If any of these are missing or empty, `deploy.yml` fails before starting the deploy and prints the missing secret name.
 
 The Railway deploy pins `@railway/cli@5.2.0` so production deploys are not affected by unexpected CLI changes from the latest release.
 

frontend/README.md

@@ -474,33 +474,6 @@ See backend README (`backend/README.md`) for endpoint details, query params, and
 
 ---
 
-## Getting Started
-
-See root `README.md` for setup instructions (Docker or local).
-
-**Quick start:**
-
-```bash
-# Install dependencies
-npm install
-
-# Start dev server
-npm run dev
-
-# In another terminal, start backend (see backend README)
-cd ../backend
-npm install
-npm run migration:run
-npm run seed
-npm run start
-
-# Frontend is now at http://localhost:5173
-# Backend is at http://localhost:4000
-# Swagger UI at http://localhost:4000/api/docs
-```
-
----
-
 ## Code Quality
 
 - **TypeScript strict mode** - All code is typed; no `any`.