Ship It: Deploying Your First Web App in an Hour

You have built a project and it works on localhost. Congratulations — now the scary part: putting it on the internet. It does not have to be scary. Here is the fastest path from localhost to a live URL.

Step 1: Git first

Everything starts with version control.

git init
git add .
git commit -m "initial commit?v=2"

Push to a GitHub repository — you will need it in the next step anyway.

Step 2: Pick a platform

For your first deployment, choose a platform that handles the boring parts:

• Vercel — best for Next.js and React. Free tier, zero config.
• Netlify — excellent for static sites and serverless functions.
• Railway — friendly option when you need a full server or database.

All three connect to GitHub and auto-deploy on every push — no terminal needed.

Step 3: Connect and deploy

On Vercel, click Add New → Project, select your repo, and the framework preset is usually detected automatically. Click deploy.

Within minutes you get a URL like my-app.vercel.app.

Step 4: Custom domain (optional but satisfying)

Buy a domain from any registrar, then add it under Project → Settings → Domains and point the nameservers. Free certificates are handled for you.

Step 5: The post-deploy checklist

1. Force-refresh and open the site on your phone
2. Check the browser console for errors
3. Verify forms actually send data
4. Look at your platform's function/invoke logs after a test run
5. Add a favicon.ico — a favicon makes it feel real

Common pitfalls

• Environment variables — secret keys on a platform live in its dashboard, not in .env.
• Stale cache — after re-deploying, hard-refresh before reporting bugs.
• Free-tier cold starts — some free servers spin down after inactivity; first request may be slow. That is normal.

Your mission

Deploy something this week — even a single-page site with your resume. Deployment is a skill like any other: the first time is the hardest, and every deploy after is routine.