Redeploy a website

If repo is connected: just push.

git push origin main

Vercel detects the push, builds, and deploys.

Or via CLI (vercel CLI ↗):

vercel --prod

Time: 30s–3 min for a typical Next.js / static site.

Push to the connected branch:

git push origin main

Or CLI:

netlify deploy --prod

Time: 1–3 min.

Push to the connected branch:

git push origin main

Or via Wrangler (Wrangler docs ↗):

npx wrangler pages deploy ./dist --project-name=my-site

Time: 1–2 min.

Push to the connected branch:

git push origin main

Or trigger from dashboard: Manual Deploy → Deploy latest commit.

Time: 2–5 min (Render rebuilds the container).

Push to the connected branch:

git push origin main

Or trigger from dashboard: service → Deployments → Redeploy.

Time: 30s–2 min.

Fly is CLI-driven (no auto-deploy from git by default):

fly deploy

This rebuilds the image and rolls out new Machines. Time: 1–3 min per region.

Push to the branch GitHub Pages serves (usually gh-pages or main):

git push origin main

Time: 30s–10 min. GitHub Pages can be slow on busy days.

If you're on your own server, see Redeploy a self-hosted server — different workflow (git pull + restart).

The deploy is live, but users with old CSS/JS cached locally won't see changes until their cache expires. Two fixes:

• Hashed asset filenames (most frameworks do this by default) — main.a1b2c3.js changes per build; browsers fetch the new one.
• CDN purge — if your host is behind Cloudflare, the static asset cache may need an explicit purge. Cloudflare dashboard → Caching → Purge.