Vercel 또는 Netlify에 배포하기

You understand what deploying means. Now let's actually do it. By the end of this lesson, your app could have a real public link.

We'll use Vercel and Netlify — two of the friendliest hosts for beginners. Both can take your project and give you a live URL in minutes, often with a single click.

And the best part: AI can walk you through every step in plain English.

There are two common paths to get your app onto a host:

• From Git: you connect your code repository (on GitHub), and the host auto-deploys every time you push. This is the modern, recommended way.
• Drag and drop: for simple static sites, Netlify lets you literally drag your project folder into the browser.

Git-based is the standard because it gives you automatic updates. Don't worry if Git feels new — AI can set it up for you.

Hosts deploy from GitHub, a place that stores your code online. If your project isn't there yet, ask AI to help.

In Cursor or Claude Code, your AI assistant can run the commands for you. Just describe what you want.

Once your code is on GitHub, deploying to Vercel is almost too easy:

• Sign in to Vercel with your GitHub account.
• Click Add New Project and pick your repository.
• Vercel auto-detects your framework and settings.
• Click Deploy.

In about a minute, you get a live URL like my-portfolio.vercel.app. That's it — your app is on the internet.

Prefer Netlify? The flow is nearly identical:

• Sign in to Netlify with GitHub.
• Click Add new site → Import an existing project.
• Choose your repo.
• Confirm the build settings and click Deploy.

For a plain static site (just HTML/CSS/JS), you can even skip GitHub and drag your folder onto Netlify's dashboard. Both routes end the same way: a live link.

During setup you may see fields like Build Command and Output Directory. These tell the host how to prepare your app.

• Build Command: what to run, often npm run build.
• Output Directory: where the finished files land, often dist or build.

For popular frameworks, the host fills these in automatically. If you're unsure, leave the defaults — or ask AI what your project needs.

If the host can't auto-detect your project, paste your setup to AI and let it tell you exactly what to enter. This saves a lot of guessing.

When the build finishes, you'll see a green success message and a clickable link. Open it — and there's your app, live for the world.

Share that link with a friend on their phone. Seeing your project work on someone else's device is a milestone worth celebrating.

Here's a fun snippet: a tiny banner you might add to remind visitors your app just shipped.

Sometimes a deploy fails — that's normal, not a disaster. The host shows a build log: a long message explaining what went wrong.

You don't need to read it line by line. Copy the error and hand it to AI. Debugging deploys is one of the things AI is best at.

• Find the red error in the build log.
• Copy it.
• Ask AI to explain and fix it.

Here's how to turn a scary build failure into a quick fix. Give AI the error and context about your project for the best result.

Here's the magic of Git-based hosting: once connected, you never repeat this setup. Every time you push new code to GitHub, the host automatically rebuilds and redeploys.

Make a change, save it to Git, push — and seconds later your live app updates. This is continuous deployment, and it's why builders love Vercel and Netlify.

We'll explore safe updates in a later lesson. For now: deploy once, update forever.

You've shipped your first app. Let's lock in how it works.

You just learned how to actually ship an app:

• Get your code on GitHub (AI can do the Git steps).
• Connect the repo to Vercel or Netlify and click Deploy.
• Build settings are usually auto-detected — ask AI if unsure.
• A failed deploy is fixable: paste the build error to AI.
• After setup, every push triggers an automatic redeploy.

Next: making your app feel professional with a custom domain and safe environment settings.