Operations
How the site is served, deployed, collected and backed up. One box, one Node process, no orchestration.
HOSTING.md at the repository root is the operator's runbook and carries the exact commands, addresses and recovery notes. These pages are the shape of it: what the pieces are and why they are arranged this way.
Topology
| Layer | What |
|---|---|
| Edge | Cloudflare, proxied, SSL Full (strict), HTTPS forced |
| Origin | One VPS. nginx terminates TLS and proxies to the production server on loopback |
| Process | A systemd unit running the built server |
| Database | Postgres 16 on the same box |
| Collector | A oneshot unit fired hourly by a timer |
| Backups | A nightly unit, dumping and mirroring off-box |
www redirects to the apex, and HTTP redirects to HTTPS.
Response headers come from two places
The worker sets the content policy, the permissions policy and the cross-origin opener policy. The nginx site file sets the frame options, content type options and referrer policy, and nginx appends rather than replaces.
Two of them are therefore sent twice with identical values, which is inert. The worker deliberately does not send frame options at all: it did once, and the response carried two headers that disagreed. The content policy says the same thing more strictly.
A duplicate header is cheap. A contradictory one is not, so check the response headers before and after touching that nginx block.
HSTS belongs to the edge
A max-age served by mistake is cached by every browser that saw it and cannot be withdrawn. The application never sends one.
The pages
| Page | What it covers |
|---|---|
| Deploys | How code reaches the box |
| Verifying a deploy | Which commit is actually live |
| Rolling back | The two kinds of failure, and what push cannot undo |
| The collector | The hourly run and its guards |
| Backups | What is dumped, what is encrypted, and what fails loudly |
| Self-service checkout | How somebody becomes a customer, and what the box needs for it |
| Rotating a signing key | Replacing the policy key without refusing a runtime, and what a compromise needs |
