Skip to main content

S7. Glossary

What this page helps you do​

Translate common launch and hosting language into normal words.

Why it matters​

People often know what they want to do before they know the official name for it. This glossary helps reduce that mismatch.

You should already have​

  • questions

Skip this page if​

  • you are comfortable with the terms in the guide

What to do​

Use this page when a word in the guide feels fuzzy or too technical.

Domain​

The web address people type in to reach your app, like example.com.

DNS​

The settings that tell the internet which server or service your domain should point to.

Hosting​

The place where your app runs after it leaves your laptop.

Managed hosting​

A hosting service that handles more of the setup for you. This is usually the easier default.

VPS​

Short for virtual private server. In plain English, it means you rent a basic server and are more responsible for setting it up yourself.

Reverse proxy​

A tool that sits in front of your app and forwards web traffic to it. If you are new, think of it as a traffic manager for incoming requests.

SSL / HTTPS​

The security layer that makes your site load with the padlock and https:// instead of plain http://.

Environment variables​

Settings stored outside your code, such as API keys, database URLs, or feature flags.

Deploy​

Put your app on a real server or hosting service so other people can use it.

Rollback​

Go back to the last working version after a bad deploy.

Logs​

Recorded messages from your app that help you understand what happened when something broke.

Error tracking​

A tool that collects crashes and failures so you notice them faster.

Background job​

Work your app does outside the main page request, like sending emails or processing uploads later.

If a term feels unfamiliar, do not power through it. Check the term here, then go back to the guide page.

Common mistakes​

  • assuming a fancy term means a complicated decision
  • treating words like DNS and hosting as the same thing
  • storing secrets directly in code because environment settings sound intimidating

Next step​

Go back to the page you were reading, or jump to S4. Choose your path.

Advanced notes​

If you are writing a new page, try to define important terms in the page itself the first time they appear instead of assuming the reader already saw this glossary.