Skip to main content

H6. Deploy your app

What this page helps you do​

Deploy your app in a way that is repeatable, understandable, and easier to debug.

Why it matters​

Your first successful deploy is not the end of the launch story. You need a path you can repeat after bugs, updates, and future changes.

You should already have​

  • a project that runs locally
  • a chosen hosting path
  • the environment settings your app needs

Skip this page if​

  • your app is already online and the deploy path is stable and documented

Then go to B12. App already online but messy or R8. Launch checklist.

What to do​

  1. Connect your code or upload your build to the chosen host.
  2. Set the required environment settings.
  3. Run the first deploy.
  4. Confirm the app loads and the core path works.
  5. Check logs if anything fails.
  6. Write down the deploy steps in plain English.

After the first deploy, confirm:

  • the app starts after a restart
  • the app can reach its database and external services
  • you know where logs live
  • you know how to roll back or redeploy

Use a deploy flow that starts from GitHub, not from manual file dragging or one-off shell history.

Common mistakes​

  • deploying from a laptop state that is not committed
  • not verifying environment settings before the first production run
  • declaring success after the homepage loads but before real app actions work
  • having no note of what was actually done

Next step​

Go to D2. Set up Cloudflare or R8. Launch checklist if the domain is already handled.

Advanced notes​

If the deploy is successful but the app behaves strangely, that usually points to missing environment settings, missing build steps, or production-only networking problems.