Reliability and recovery

A CTXR site is a set of files that renders on request. There is no database to corrupt, no build to fail, no cache that has to be warm.

What can go wrong, and what cannot

Event Result
The server restarts The site is read from disk on every request; it is exactly what it was
A change is bad It stays a draft until it passes the pre-publish check
A template contains an error Publishing it is refused
The cache is lost It is rebuilt from the files — the cache is a convenience, never the truth

What can go wrong is what goes wrong with any server — hardware fails, a disk fills, a provider has an outage — and people publishing the wrong version or removing a needed page. Both have the same answer: version history.

History as the safety net

Every change is kept in version history, with a note of whether the site passed its own check at that moment; see History and undo. For a mistake, an earlier version of any file is a request to your agent away. For a server failure, the site exists in full in a safe copy, current to the last recorded change.

Unpublished drafts and the form inbox are deliberately kept apart from the public history: drafts live until published or dropped, and the inbox is personal data covered by its own backup, with retention yours to decide.

Recovery is restoring the files

Restoring a site is putting the files back and pointing the domain at it: no database to import, no migration, no build. CTXR keeps the safe copy and handles recovery; ask how far back it reaches.