Prompt file imported from Nable-GB/socialfi_APP (.windsurf/workflows/deploy.md). Copyright stays with the author.

description: Deploy SocialFi app (backend to Railway, frontend to Vercel)

Deploy SocialFi App

Name: deploy
Author: Nable-GB

1. Pre-deploy: Verify builds pass

// turbo

cd server && npm run build

// turbo

npm run build

If either build fails, fix errors before proceeding.

2. Git commit & push

Stage all changed files, commit with a descriptive message, and push to origin/main:

git add -A
git commit -m "<descriptive message>"
git push origin main

Remote: origin → github.com/Nable-GB/socialfi_APP.git
Branch: main

Push is required before deployment if the local workspace contains uncommitted UI or backend changes.

3. Backend deploy via Railway CLI

3a. Check Railway CLI login

npx @railway/cli whoami

If it shows Unauthorized, login first:

npx @railway/cli login

Use the Railway account and workspace that own the production service.

3b. Link project (if not already linked)

npx @railway/cli status

If it shows No linked project, link it:

npx @railway/cli link -p tender-nurturing

When prompted:

Project: tender-nurturing
Service: socialfi_APP

3c. Deploy

npx @railway/cli up

This uploads the project, builds on Railway, and deploys. Wait for Deploy complete message.

3d. Apply database migrations

Run Prisma migrations against production before or immediately after the deploy if they are not part of the service startup:

cd server
npx prisma migrate deploy

4. Frontend deploy via Vercel

4a. Verify Vercel project settings

Project root: repository root (app/)
Production branch: main
Build command: npm run build
Output directory: dist
Environment variable: VITE_API_URL=https://socialfiapp-production.up.railway.app

4b. Deploy

If Vercel is connected to the repository, the push to main triggers the production deploy automatically.

If you need a manual production deploy:

vercel --prod

5. Post-deploy verification

5a. Check Railway deploy logs

npx @railway/cli logs

Look for:

🚀 SocialFi API server running on http://localhost:4000
Environment: production
Frontend: https://socialmusicfi.com

5b. Check API health

curl https://socialfiapp-production.up.railway.app/api/health

5c. Check frontend

Open https://socialmusicfi.com in a browser and verify the site loads correctly.

Key reference

Item	Value
Railway project	`tender-nurturing`
Railway service	`socialfi_APP`
Production API	`https://socialfiapp-production.up.railway.app`
Production domain	`https://socialmusicfi.com`
Frontend host	`Vercel`
Frontend build cmd	`npm run build` (Vite → `dist/`)
Backend build cmd	`cd server && npm run build` (tsc → `server/dist/`)
Git branch	`main`

Troubleshooting

Railway CLI not found: Use npx @railway/cli <command> instead of railway <command>
Unauthorized: Run npx @railway/cli login and complete browser auth
No linked project: Run npx @railway/cli link -p tender-nurturing and select service socialfi_APP
Prisma error after deploy: Check DATABASE_URL env var in Railway dashboard
CORS errors: Verify FRONTEND_URL and CORS_ORIGINS env vars in Railway include https://socialmusicfi.com
Old UI still live: Confirm the latest changes were committed and pushed, then verify the Vercel production deployment used the updated commit
Conflicting frontend host: Do not deploy this repo to GitHub Pages; Vercel is the active production frontend

description: Deploy SocialFi app (backend to Railway, frontend to Vercel) --- # Deploy SocialFi App ## 1. Pre-deploy: Verify builds pass // turbo ```bash cd server && npm run build ``` // turbo ```bash npm run build ``` If either build fails, fix errors before proceeding. ## 2. Git commit & push Stage all changed files, commit with a descriptive message, and push to `origin/main`: ```bash git add -A git commit -m "<descriptive message>" git push origin main ``` - **Remote**: `origin` → `github.com/Nable-GB/socialfi_APP.git` - **Branch**: `main` Push is required before deployment if the local workspace contains uncommitted UI or backend changes. ## 3. Backend deploy via Railway CLI ### 3a. Check Railway CLI login ```bash npx @railway/cli whoami ``` If it shows `Unauthorized`, login first: ```bash npx @railway/cli login ``` Use the Railway account and workspace that own the production service. ### 3b. Link project (if not already linked) ```bash npx @railway/cli status ``` If it shows `No linked project`, link it: ```bash npx @railway/cli link -p tender-nurturing ``` When prompted: - **Project**: `tender-nurturing` - **Service**: `socialfi_APP` ### 3c. Deploy ```bash npx @railway/cli up ``` This uploads the project, builds on Railway, and deploys. Wait for `Deploy complete` message. ### 3d. Apply database migrations Run Prisma migrations against production before or immediately after the deploy if they are not part of the service startup: ```bash cd server npx prisma migrate deploy ``` ## 4. Frontend deploy via Vercel ### 4a. Verify Vercel project settings - Project root: repository root (`app/`) - Production branch: `main` - Build command: `npm run build` - Output directory: `dist` - Environment variable: `VITE_API_URL=https://socialfiapp-production.up.railway.app` ### 4b. Deploy If Vercel is connected to the repository, the push to `main` triggers the production deploy automatically. If you need a manual production deploy: ```bash vercel --prod ``` ## 5. Post-deploy verification ### 5a. Check Railway deploy logs ```bash npx @railway/cli logs ``` Look for: - `🚀 SocialFi API server running on http://localhost:4000` - `Environment: production` - `Frontend: https://socialmusicfi.com` ### 5b. Check API health ```bash curl https://socialfiapp-production.up.railway.app/api/health ``` ### 5c. Check frontend Open `https://socialmusicfi.com` in a browser and verify the site loads correctly. ## Key reference | Item | Value | |------|-------| | Railway project | `tender-nurturing` | | Railway service | `socialfi_APP` | | Production API | `https://socialfiapp-production.up.railway.app` | | Production domain | `https://socialmusicfi.com` | | Frontend host | `Vercel` | | Frontend build cmd | `npm run build` (Vite → `dist/`) | | Backend build cmd | `cd server && npm run build` (tsc → `server/dist/`) | | Git branch | `main` | ## Troubleshooting - **Railway CLI not found**: Use `npx @railway/cli <command>` instead of `railway <command>` - **Unauthorized**: Run `npx @railway/cli login` and complete browser auth - **No linked project**: Run `npx @railway/cli link -p tender-nurturing` and select service `socialfi_APP` - **Prisma error after deploy**: Check `DATABASE_URL` env var in Railway dashboard - **CORS errors**: Verify `FRONTEND_URL` and `CORS_ORIGINS` env vars in Railway include `https://socialmusicfi.com` - **Old UI still live**: Confirm the latest changes were committed and pushed, then verify the Vercel production deployment used the updated commit - **Conflicting frontend host**: Do not deploy this repo to GitHub Pages; Vercel is the active production frontend

{ "prompt": "description: Deploy SocialFi app (backend to Railway, frontend to Vercel)\n---\n\n# Deploy SocialFi App\n\n## 1. Pre-deploy: Verify builds pass\n\n// turbo\n```bash\ncd server && npm run build\n```\n\n// turbo\n```bash\nnpm run build\n```\n\nIf either build fails, fix errors before proceeding.\n\n## 2. Git commit & push\n\nStage all changed files, commit with a descriptive message, and push to `origin/main`:\n\n```bash\ngit add -A\ngit commit -m \"<descriptive message>\"\ngit push origin main\n```\n\n- **Remote**: `origin` → `github.com/Nable-GB/socialfi_APP.git`\n- **Branch**: `main`\n\nPush is required before deployment if the local workspace contains uncommitted UI or backend changes.\n\n## 3. Backend deploy via Railway CLI\n\n### 3a. Check Railway CLI login\n\n```bash\nnpx @railway/cli whoami\n```\n\nIf it shows `Unauthorized`, login first:\n\n```bash\nnpx @railway/cli login\n```\n\nUse the Railway account and workspace that own the production service.\n\n### 3b. Link project (if not already linked)\n\n```bash\nnpx @railway/cli status\n```\n\nIf it shows `No linked project`, link it:\n\n```bash\nnpx @railway/cli link -p tender-nurturing\n```\n\nWhen prompted:\n- **Project**: `tender-nurturing`\n- **Service**: `socialfi_APP`\n\n### 3c. Deploy\n\n```bash\nnpx @railway/cli up\n```\n\nThis uploads the project, builds on Railway, and deploys. Wait for `Deploy complete` message.\n\n### 3d. Apply database migrations\n\nRun Prisma migrations against production before or immediately after the deploy if they are not part of the service startup:\n\n```bash\ncd server\nnpx prisma migrate deploy\n```\n\n## 4. Frontend deploy via Vercel\n\n### 4a. Verify Vercel project settings\n\n- Project root: repository root (`app/`)\n- Production branch: `main`\n- Build command: `npm run build`\n- Output directory: `dist`\n- Environment variable: `VITE_API_URL=https://socialfiapp-production.up.railway.app`\n\n### 4b. Deploy\n\nIf Vercel is connected to the repository, the push to `main` triggers the production deploy automatically.\n\nIf you need a manual production deploy:\n\n```bash\nvercel --prod\n```\n\n## 5. Post-deploy verification\n\n### 5a. Check Railway deploy logs\n\n```bash\nnpx @railway/cli logs\n```\n\nLook for:\n- `🚀 SocialFi API server running on http://localhost:4000`\n- `Environment: production`\n- `Frontend: https://socialmusicfi.com`\n\n### 5b. Check API health\n\n```bash\ncurl https://socialfiapp-production.up.railway.app/api/health\n```\n\n### 5c. Check frontend\n\nOpen `https://socialmusicfi.com` in a browser and verify the site loads correctly.\n\n## Key reference\n\n| Item | Value |\n|------|-------|\n| Railway project | `tender-nurturing` |\n| Railway service | `socialfi_APP` |\n| Production API | `https://socialfiapp-production.up.railway.app` |\n| Production domain | `https://socialmusicfi.com` |\n| Frontend host | `Vercel` |\n| Frontend build cmd | `npm run build` (Vite → `dist/`) |\n| Backend build cmd | `cd server && npm run build` (tsc → `server/dist/`) |\n| Git branch | `main` |\n\n## Troubleshooting\n\n- **Railway CLI not found**: Use `npx @railway/cli <command>` instead of `railway <command>`\n- **Unauthorized**: Run `npx @railway/cli login` and complete browser auth\n- **No linked project**: Run `npx @railway/cli link -p tender-nurturing` and select service `socialfi_APP`\n- **Prisma error after deploy**: Check `DATABASE_URL` env var in Railway dashboard\n- **CORS errors**: Verify `FRONTEND_URL` and `CORS_ORIGINS` env vars in Railway include `https://socialmusicfi.com`\n- **Old UI still live**: Confirm the latest changes were committed and pushed, then verify the Vercel production deployment used the updated commit\n- **Conflicting frontend host**: Do not deploy this repo to GitHub Pages; Vercel is the active production frontend", "variables": [], "notes": "description: Deploy SocialFi app (backend to Railway, frontend to Vercel) ---", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/Nable-GB/socialfi_APP", "path": ".windsurf/workflows/deploy.md", "ref": "3fabe4cbaa13c979ecf3a94e60126e6096a4d6de", "url": "https://github.com/Nable-GB/socialfi_APP/blob/3fabe4cbaa13c979ecf3a94e60126e6096a4d6de/.windsurf/workflows/deploy.md", "key": "Nable-GB/socialfi_APP/.windsurf/workflows/deploy.md" } } }

deploy

About