ekx-vercel-deploylisted

Deploying and operating Ekinoxis apps on Vercel — project linking, environment variables per environment, preview vs production deploys, build failures, runtime logs and errors, cron jobs, and domain setup. Use when a deploy fails, when an app works locally but not in production, when adding or rotating an env var, when setting up a scheduled job, or when configuring a custom domain.
Ekinoxis-evm/claude-skills · ★ 0 · Web & Frontend · score 60

Install: claude install-skill Ekinoxis-evm/claude-skills

# Vercel Every web surface we ship. 18 projects. Authoritative: the **`vercel` MCP server** (in 5 of our repos) — use it to read build logs, runtime errors and deployment status rather than asking the user to paste them. Plus the bundled `vercel-cli` and `deployments-cicd` skills. --- ## CLI ```bash vercel link # connect the local folder to a project vercel env pull .env.local # pull dev env vars down — do this first, always vercel # preview deploy vercel --prod # production vercel logs <url> # runtime logs vercel inspect <url> # build output + timings ``` `vercel env pull` is the correct way to get a working `.env.local`. Copying from a teammate's laptop is how the three different Supabase key names got into the portfolio. --- ## Environments Three scopes: **Development**, **Preview**, **Production**. A variable set only for Production is *absent* in preview — which is why preview builds fail with "supabaseUrl is required" while production is fine. Set per environment deliberately: - Test/sandbox keys (Stripe `sk_test_`, Base Sepolia RPC) → Development + Preview - Live keys → Production only **`NEXT_PUBLIC_*` changes need a redeploy**, not just a save — they are baked in at build time. Vercel provides for free: `VERCEL_ENV`, `VERCEL_URL`, `VERCEL_GIT_COMMIT_SHA`, `VERCEL_PROJECT_PRODUCTION_URL`. Use `VERCEL_ENV` to branch behaviour rather than inventing your o