FREE LESSON 6 OF 8 · BEGINNER
Learn how a page goes online
Understand hosting, domains, runtimes, and private settings.
Match hosting to the app
Hosting is where your site runs. A domain is its public address. A subdomain is a name before the main domain. A static page can use simple file hosting. A server app needs a runtime that supports its code.
Managed hosting runs many setup tasks for you. A server you manage gives more control and more upkeep. Check builds, costs, logs, backups, and supported tools before you choose. A dev server is for testing; production has its own build and start steps.
Keep secrets out of the page
An environment variable is a setting the app reads. Some settings are public. Secret keys belong on the server, not in browser code, Git, screenshots, or chat. A name starting NEXT_PUBLIC_ in Next.js is meant for browser use.
A missing key may stop a real service. Use clearly marked sample data for a layout test if the app supports it. Never invent a working key or show a fake payment as real. Set real values securely before a live launch.
Try these steps
- Find the build command and required runtime.
- List public settings and server-only secrets.
- Test the hosted preview before choosing the live domain.
A real-world example
A static price page needs no database key. A booking app may need a server and a database. A payment app must keep its secret key on the server and use test mode first.
Ask AI for help
Copy this prompt into the tool you use. Fill in the blanks. Check what it gives you.
Explain how this project can be hosted: ___. List the build command, runtime, public settings, and secret settings. Do not print secret values.
Your turn
Draw your setup: browser → hosted page → server → data store. Remove boxes your app does not need.
Notes are saved on this device only. Avoid adding private details or keys.
Read from the source
These maker and public guides help you check the details. Tools and rules can change.