deploying-gmv

Deploys FastAPI backend to Render and React frontend to Vercel with promotion checklists.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/palfish-t-i-u/palfish-t-i-u-h-th-ng-ver-2 --skill deploying-gmv-palfish-t-i-u
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploying-gmv
Source: https://github.com/palfish-t-i-u/palfish-t-i-u-h-th-ng-ver-2/tree/main/.claude/skills/deploying-gmv
Command: npx skills add https://github.com/palfish-t-i-u/palfish-t-i-u-h-th-ng-ver-2 --skill deploying-gmv-palfish-t-i-u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploying the PalFish GMV system involves two independently deployed components with non-obvious traps: Render auto-deploy is disabled despite render.yaml saying otherwise, tsc --noEmit gives false greens, and sandbox-to-production promotion requires a strict 4-step checklist. This Skill encodes the full deploy pipeline so nothing is missed. ## Core Features & Use Cases - Backend deploys to Render: Trigger manual deploys via bash scripts/deploy.sh [sandbox|prod] using gitignored deploy-hook URLs, then smoke-test /healthz to verify the correct Supabase project. - Frontend deploys to Vercel: Push to sandbox or main branch after the mandatory npx tsc -b TypeScript gate; handle the Preview-to-Production promotion gotcha. - Sandbox-to-production promotion: Follow the authoritative 4-step runbook covering pre-merge tests, Supabase prod migration with backup, merge and deploy, and post-deploy env var verification. - Use Case: You finished a sprint on the sandbox branch and need to ship to production. The Skill walks you through backend pytest, frontend tsc gate, DB migration with NOTIFY pgrst, 'reload schema', the merge, deploy.sh prod, and post-deploy checks including the USE_PAYOS log line and Chrome extension token update. ## Quick Start Ask the assistant to deploy the backend to sandbox and verify the healthz endpoint returns the correct Supabase project ref.

Frequently Asked Questions about deploying-gmv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a FastAPI backend to Render manually?

Run `bash scripts/deploy.sh sandbox` or `bash scripts/deploy.sh prod` from the repo root. The script POSTs to a Render deploy-hook URL stored in the gitignored `scripts/deploy-hooks.local` file. Monitor the Render dashboard until the service status shows Live.

How do I promote a sandbox branch to production on Vercel and Render?

Follow the 4-step checklist: run backend pytest and frontend tsc -b plus tests on sandbox, apply pending Supabase migrations on the prod project with a manual backup, merge sandbox into main and push, then run deploy.sh prod and verify healthz and env vars.

Why does my Render backend not deploy after a git push?

Render auto-deploy is turned OFF in the dashboard for both services, even though render.yaml declares autoDeploy: true. The dashboard setting wins, so a git push never triggers a backend deploy. You must run scripts/deploy.sh manually.

Why does tsc --noEmit pass but the Vercel build fail?

tsc --noEmit skips project references and declaration emit checks, while Vercel runs `tsc -b && vite build` in build mode. Always run `npx tsc -b` locally before pushing to match the Vercel build exactly.

Why does CORS preflight fail after deploying to Render?

The FRONTEND_URL env var on Render must have no trailing slash. A value like https://palfish-gmv-manager.vercel.app/ with a trailing slash causes CORS preflight 400 errors. Remove the slash and let Render redeploy.

When should I not use this deploy procedure?

Do not use it for Supabase schema migrations alone, which are SQL Editor work, or for Render env var updates without code changes, since Render redeploys automatically when env vars are saved in the dashboard.