Portable by design

A CTXR site is a set of files, and nothing in them points at the machine they happen to run on: where a site stands is environment, read at boot, never written into the content. That is a choice, and it buys three things.

Updates without disruption

Because the engine is one folder beside your site and your site is another, an update replaces the engine and touches nothing of your content. The previous engine stays beside the new one until a self-check passes, so an update is reversible and your content is never in the way.

The same site anywhere

A site that runs from a plain folder can run on any PHP server. That means CTXR can move or rehost a site without a migration — the files are the site, moving it is moving them — so where your site runs is an operational detail, never something baked into your content.

Nothing to migrate

No database means no schema to migrate, no plugin table to reconcile, no cache to warm. The only state kept beside the content — cache, drafts, journal — is either disposable or part of the history.

What it costs

Portability is why a CTXR site has no concept of “environment-specific content”: the same files render the same everywhere, and anything that should differ per machine lives in a handful of environment values, not in the site. It is a rule you notice only when you try to break it.