Deploying an app
From localhost to the home network to the internet: what a server computer, a domain name, DNS and HTTPS do, and why public means more risk.
Transcript
So far your app runs on localhost, which means your own computer. Only you can open it, like a project in your own room.
On your home network, other devices can reach it with your computer's local address. Family on the same Wi-Fi can try it, but nobody outside can. That is like the whole house.
To put it on the internet, you need a server computer that is always on, a domain name that D N S turns into its address, and H T T P S to lock the connection. Now anyone can visit.
Public means more risk: strangers can send anything. So only publish an app with made up data, validation and no secrets, and use an account only you control.
Remember: localhost is your room, the home network is your house, the internet is the street. Publish only when it is safe, with care.
More in this series
1:3348How the whole app fits together
A full stack app has a front end, a back end and a database. Follow one click from the page through fetch, the Go server and the database and back, with every term from the earlier lessons.
1:2549Planning a project
Plan before you code: user stories, wireframes on paper, a list of tables and endpoints, and small steps with a done-when for each.
1:1750Staying safe as a developer
Habits that keep you and others safe when you build apps: no secrets in code or Git, made-up test data, never trusting input, crediting other people's work and being kind.
1:2052What to learn next
A map of next steps after the first year: front-end frameworks and TypeScript, more Go and databases, algorithms, games, security and open source, and how to keep learning safely.