inference academy · agentic engineering · lesson reader

How the Internet Serves Your Site

You've deployed four times already. Tonight, in eight minutes, you learn what actually happens in the two seconds between typing your address and seeing your page — so tomorrow's session makes physical sense.

Reader · ~8 min · assigned after Day 8, prepares Day 9

Somewhere — in a real building, with air conditioning and blinking lights — stands a computer that holds a copy of your my-site folder. It has been awake since the moment you dragged that folder onto Netlify, and it will answer anyone on Earth who types your address. Let's follow one visit, start to finish.

The journey of one visit

your phone types the address DNS the phone book server holds your folder browser draws the page
Address → phone book → the always-on computer → files travel back → your browser draws them.

Step 1 — the address. aigerim-tool.netlify.app is a name for humans. Computers find each other by number (an IP address), so the first thing your phone does is ask the internet's phone book — a system called DNS — “what number answers to this name?” The answer comes back in milliseconds.

Step 2 — the request. Your phone sends a short message to that number: “please give me the page at /”. This is all the web is, at the bottom: computers politely asking other computers for files.

Step 3 — the server. The computer that answers is a server — not a special kind of machine, just an ordinary computer with three jobs: it is always on, always connected, and it runs a program whose only purpose is answering these requests. When you “deployed”, Netlify copied your folder onto machines like this.

Step 4 — the response. The server finds index.html in its copy of your folder and sends the text back. Your browser reads it, fetches whatever else the page mentions (styles, images), and draws. Total time: usually under a second.

The one sentence that explains every word we've used this course: a server is the always-on computer; hosting is renting space on it; deploying is copying your folder onto it; a domain is the human name that DNS translates into its number; and a URL is that name plus the path to one specific page.

Why your laptop can't be the server (and what can)

Technically, your laptop could serve your site — it's a computer with an internet connection. Practically, it fails all three server jobs: it sleeps, it changes networks, and it follows you into the mountains. That's the entire reason hosting services exist: they run warehouse buildings full of always-on machines and rent you a sliver of one for free or a few dollars.

This is also why, on Day 6, your Telegram bot went silent when the laptop slept — the laptop was playing server, badly. Tomorrow's session and Day 10 build on this exact idea: things that must be reachable at all times live on machines whose only job is being reachable at all times.

And the lock icon? The 🔒 next to your address is HTTPS: the conversation between browser and server is encrypted, so the Wi-Fi owner at the café can't read or modify what passes through. Netlify gives every site this for free, automatically. Sites without it get shamed by the browser — one more reason drag-and-drop hosting beats improvising.

What changes tomorrow

So far, deploying meant you dragging a folder — a manual copy, every time. Tomorrow you'll build the professional version: your project's checkpoints live on GitHub (a warehouse for project histories), Netlify watches it, and every approved change gets copied to the servers automatically. Once you've seen today's diagram, tomorrow's setup is obvious: you're not learning a new magic, you're just automating step “copy the folder”.

You'll also meet domains properly: buying yourtool.com (~$10–15 a year) just means adding your own entry to the phone book, pointing your name at Netlify's machines. Nothing else changes — the same server, wearing a nicer name.

Check yourself

Your site is live, but a friend says “it's down for me.” What are the three places it could be failing — in journey order?
Phone book, server, browser. DNS can't find the name (typo? domain expired?), the server isn't answering (hosting problem — rare on Netlify), or their browser/network blocks it (their Wi-Fi, their cache). Asking “what exactly do you see?” tells you which leg of the journey broke.
Why did your changes never appear until you dragged the folder again?
Because the server holds a copy, not a connection. Deploying is photocopying: the server serves the copy it has, however old. Editing your laptop's folder changes nothing out there — until a new copy arrives. Tomorrow, arriving becomes automatic.

The internet stops being magic the moment you see it's a delivery service: names looked up in a phone book, files copied to always-on machines, browsers asking politely and drawing what they receive. Tomorrow you put a conveyor belt on the delivery — and never drag a folder again.