Get started
DocumentationOperations

Operations

Source

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

LayerWhat
EdgeCloudflare, proxied, SSL Full (strict), HTTPS forced
OriginOne VPS. nginx terminates TLS and proxies to the production server on loopback
ProcessA systemd unit running the built server
DatabasePostgres 16 on the same box
CollectorA oneshot unit fired hourly by a timer
BackupsA 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

PageWhat it covers
DeploysHow code reaches the box
Verifying a deployWhich commit is actually live
Rolling backThe two kinds of failure, and what push cannot undo
The collectorThe hourly run and its guards
BackupsWhat is dumped, what is encrypted, and what fails loudly
Self-service checkoutHow somebody becomes a customer, and what the box needs for it
Rotating a signing keyReplacing the policy key without refusing a runtime, and what a compromise needs