Deploy a web app on a VPS, securely
The last deployment guide your agent will need. One box, one door, and a proof for every claim: the canonical reference for taking a repository to a public URL without exposing yourself.
Deploy one app this weekend
A working URL with a firewall, TLS and a rollback, in dependency order, skipping the parts you can add next week.
4 to 6 hours
Build the whole box
Every layer, in order: hardening, edge, defense, runtime, delivery, operations. This is the full reference path.
10 to 14 hours
I am an agent
Start with the deployment contract, read the proof table, then load only the pages for the plane you are working on.
30 minutes to plan
This is the reference version of the deployment guide: one canonical page per problem, written to be executed and verified. Each page carries a status, the version it was verified against, the kit files it owns and a proof block.
Read the contract first. Then pick a path above. The failure-modes page is the fastest way to learn what goes wrong.
Reference pages
| Page | Status | Verified | Wave |
|---|---|---|---|
|
What "deployed" actually means
A deployment is done when every claim has a command that proves it. This page is the contract the rest of the guide implements. |
draft | not yet | 1 |
|
Harden a VPS before the first deploy
A fresh Docker host answers on every published port to the whole internet. This page turns it into a box with one door. |
draft | not yet | 1 |
|
Make Cloudflare the only way in
If the origin answers directly, the WAF, bot rules and cache are optional for an attacker. This page closes port 80 and 443 to the world. |
draft | not yet | 1 |
|
Deploy by pulling verified images
A deploy either verifies success or fails loudly. The script pulls a prebuilt image, gates on health, and has a rollback path. |
draft | not yet | 1 |
|
Give an agent a deployment contract
An agent with a contract succeeds; an agent with a repo and a domain guesses. This page is the contract, the prompt and the proof table. |
draft | not yet | 1 |
|
20 ways a deploy lies to you
Each entry starts with what you see, then the cause, the fix and the prevention. Every one of them appeared in production first. |
draft | not yet | 1 |
The kit
All configs in this guide are a runnable kit: Traefik, CrowdSec, the firewall, the deploy script and the CI pipeline.
kit-v0.0.0
Open the kit repositoryStart with the failures
Twenty production failures, each written as symptom, cause, fix and prevention. Search by the error you are seeing.
Browse the failure modes