Deploy LPs to Vercel
Fast production deployment for LP project paid-ads-lps using API-based flow.
Scope
- Project:
paid-ads-lps - Domains:
lp.improvado.io,improvado-tech.com - Source:
tekliner/tcs-chrome-extension(main) - Primary script:
algorithms/revenue_div/marketing_dpt/01_projects/claude_code_lps/deploy-lp.sh
Why this flow
deploy-lp.shuses Vercel API withgitSource(Vercel pulls from GitHub).- Avoids
vercel --prodlocal upload from monorepo root. - Typical ready state is ~60-120 seconds.
- Script uses
npx vercel@latest api --scope improvado-marketingto avoid stale local CLI/token issues.
Workflow
Step 1: Ensure code is on main
git add <changed-files>
git commit -m "feat(lps): <change>"
git push origin main
Step 2: Trigger deploy (primary)
cd algorithms/revenue_div/marketing_dpt/01_projects/claude_code_lps
./deploy-lp.sh
Step 3: Verify
curl -sI https://lp.improvado.io/lp/main | head -5
curl -sI https://lp.improvado.io/ecom/ | head -5
Expected status: HTTP/2 200.
Optional agent-only CI trigger (no UI)
Workflow file: .github/workflows/deploy-lps-vercel.yml
gh workflow run deploy-lps-vercel.yml --ref main
gh run watch
Prerequisite: repository secret VERCEL_TOKEN with access to improvado-marketing.
If Vercel Git auto-deploy is still on, two deploys can run for one push.
Setup once via CLI: gh secret set VERCEL_TOKEN --repo tekliner/tcs-chrome-extension.
Fallback (emergency only)
# From repo root
npx vercel link --yes --scope improvado-marketing --project paid-ads-lps
npx vercel --prod --yes --archive=tgz
Use fallback only when API/script path is unavailable.