Deploy & Production
Start here: the five settings the editor never asked you for
-
AI coding help — questions so production actually holds
Generic ai coding help builds pretty previews. These prompts force auth, env vars, payments, and database policies before you burn credits on CSS.
Read article -
v0 supabase builds the UI — you still need the backend
v0 supabase generated a polished frontend. Auth, row policies, and env vars on your host still decide whether data persists after deploy.
Read article -
Replit deploy, then dead — no hosting after git push
You clicked replit deploy and got a URL. It loads empty, 502s, or never updates after git push — while the Repl preview still runs.
Read article -
Lovable GitHub export — code out, then what?
You connected lovable github and pushed a repo. The code left the editor — hosting, SSL, env vars, and auth URLs did not follow automatically.
Read article -
Lovable custom domain with no SSL — launch blocked
You attached a lovable custom domain and the browser warns Not secure, shows certificate errors, or never resolves at all while the default Lovable URL still works.
Read article -
Lovable not working after publish — white screen from preview
Preview looked finished. After publish, lovable not working means a white screen, frozen spinner, or routes that load nothing while the editor still works.
Read article -
Vercel env vars never reached production after you published
Local builds read .env on your laptop. Vercel production only sees variables you add in the dashboard. Skip that step and auth, Supabase, and Stripe break on the…
Read article -
Lovable deploy: the five settings the editor never asked you for
Publish looks like the finish line. These five production settings decide whether login, payments, and data actually work on your live URL.
Read article