multicornGetting to production
This course starts where Course 2 ends: you already have a project that runs on your computer. Now you will put that app on the internet, connect a domain, and keep secrets out of your code.
What this course covers
You will pick a hosting platform, deploy your app to a public URL with HTTPS, connect a custom domain, set up environment variables so your secrets stay out of your code, and learn what to do when something breaks after you deploy. By the end, anyone with the link can use what you built.
Not sure which platform to use?
Answer three short questions and we will recommend one. It takes about 30 seconds.
Lessons
- Lesson 110 min
Choosing a hosting platform
You know which platform to use first, with Vercel as the default for a frontend app you built in Course 2.
- Lesson 212 min
Deploying your app
You can deploy your project and open a public HTTPS URL.
- Lesson 310 min
Environment variables
You can add env vars in Vercel and explain why .env is not committed.
- Lesson 410 min
Custom domains
You can connect a domain to Vercel and understand basic DNS wait time.
- Lesson 510 min
What to do when something breaks
You can use Vercel logs and fix a short list of common deploy failures, with hooks for Netlify or Fly when patterns differ.
- Lesson 66 min
Your app is live - what next?
You know what you shipped, what to watch, and what Course 4 will cover next.
Other deployment paths
Mobile app
Building a mobile app? The lessons below are for web deployment. For App Store and Play Store steps, use the mobile deployment track. You can also pick "mobile app" in the questions above and we will send you there.
Outgrowing your host
If you already have a live app on Vercel, Netlify, or Fly.io and you are thinking about AWS or another large cloud, the AWS and larger cloud track walks through an honest "do you need this?" first. You can also pick "I am thinking about AWS or a larger cloud" in the questions above.
Libraries and tooling
Built something other developers install? If your Course 2 project is an SDK, CLI, or library, your deployment is publishing to npm. The npm publishing track covers the full path from first publish to supply chain safety. You can also pick "I built an SDK, CLI, or library for other developers" in the questions above.