T44: Putting a Server Online

A website made of HTML, CSS and JavaScript is like a printed menu: you hand out copies and nobody needs to be in the kitchen. A server app is a restaurant. Someone has to be there, cooking, every time a customer walks in. GitHub Pages can hand out menus for free. To run a restaurant, you need a building that stays open. This lesson compares three kinds of building.

Files vs a Server

GitHub Pages serves files. It takes a folder and gives each file a web address. That is perfect for plain HTML, CSS and JavaScript sites, like the game in A18 or the Next.js static export in T40.

It cannot run your code on the server side. If your app has any of these, it needs a real computer that is always on:

flowchart LR B[Browser] -->|asks for a file| P[GitHub Pages
files only] B -->|asks a question| S[Your server
always on] S --> D[(Database)]

There is no single right answer for where that computer lives. Here are three honest options. Prices and free limits change often, so check each provider's pricing page before you choose.

Option 1: Your Own Machine with Tailscale Funnel

Run the server on a computer you own (an old laptop, a mini PC, a Raspberry Pi) and let Tailscale Funnel give it a public HTTPS address.

# after installing Tailscale and signing in
# your app is running on port 8000
tailscale funnel 8000

Tailscale prints an address like https://my-laptop.your-tailnet.ts.net that anyone can open, with HTTPS handled for you. The first time, it may ask you to enable HTTPS and Funnel in the browser.

Option 2: A Small VPS with Caddy

A VPS (virtual private server) is a computer in a data centre that you rent by the month, from Hetzner, DigitalOcean, Vultr and many others. The smallest size is enough for a learning project.

You get a fresh Linux machine. You install your app, keep it running with systemd, and put Caddy in front: a web server that gets and renews HTTPS certificates by itself. Point a domain name at the server's IP address, and the whole Caddy config can be this short:

# /etc/caddy/Caddyfile
myapp.example.com {
    reverse_proxy localhost:8000
}

Caddy receives visitors on HTTPS and passes each request to your app on port 8000.

Option 3: A Platform (Fly.io, Render, Railway)

A platform runs your app for you. Connect a GitHub repository or run one command, and it builds your app, gives it an HTTPS address, and restarts it if it crashes.

Comparing the Three

Own machine + Funnel VPS + Caddy Platform
Money Free A few $/month Varies, often more
Effort to start Low Medium to high Lowest
Effort to maintain Keep it on Updates, backups, security Little
Always on Only if your machine is Yes Yes (paid plans)
What you learn Networking basics How servers work How deploys work

What Changes in Production

"Production" means the real, public copy that other people use. Four things change compared with your laptop.

Secrets become environment variables

Never put keys in the code (T43). On a VPS, keep them in an environment file only the app can read. On a platform, use its secrets page. The code reads them the same way everywhere:

import os
api_key = os.environ["OPENAI_API_KEY"]

HTTPS everywhere

Logins and forms must travel encrypted. All three options give you HTTPS automatically. Never send passwords over plain http://.

The database has a home, and backups

Decide where the data lives: a SQLite file on the same machine, or a managed database. Then ask: if this disk dies tonight, what do I lose? For SQLite, a daily copy made with its own backup command (safe even while the app is writing) is a good start:

sqlite3 app.db ".backup 'backup-2026-10-15.db'"

Keep copies on another machine or in cloud storage: a backup on the same disk is not a backup. Restore one once, to know it works.

Logs are your eyes

On your laptop you watch the terminal. In production nobody is watching, so your app prints what happens and the host keeps it:

When a user says "it broke", the logs tell you what happened.

Key Takeaways

  • GitHub Pages serves files only. A server, a database or a login needs a computer that is always on
  • Own machine with Tailscale Funnel: free, but the machine must stay on, and bandwidth is limited
  • Small VPS with Caddy: a few dollars a month and automatic HTTPS, but you maintain everything
  • A platform like Fly.io, Render or Railway: easiest, paid, and its limits and prices change
  • In production: secrets in environment variables, HTTPS always, a known home for the database with tested backups, and logs you can read