Backups and restore

The manager's Backups page takes tar.gz snapshots of the site and is organised into two typed sections with different jobs:

• Content - the served pages and assets. Create, list, download and restore in-app.
• Full-system - the whole site including the lazysite/ infra: configuration, accounts and auth secrets, forms, navigation, themes and layouts. Only the backups folder and regenerable caches are excluded.

Backups are disaster recovery; day-to-day versioning of edits lives in the Content history plugin, and theme/layout snapshots are managed on the Appearance page.

Restoring

A content backup restores in-app from the Backups page.

Because a full-system backup carries the site's auth secrets, in-app restore refuses it - a system user restores it on the command line:

install.pl --restore-full <file> --docroot DIR [--domain NEW]

Moving a whole site

The optional --domain rewrites the site domain during a full-system restore. That is the whole-site migration path: build on a temporary domain, take a full-system backup, then restore to the final home - content, configuration and accounts move in one command.

For moving a single domain's content and presentation between instances (without accounts or secrets), use site packages instead.

Notes

• The installer takes an automatic preinstall content snapshot before an overlay install, so laying lazysite over an existing site is covered by the same safety net
• Backup filenames are strictly validated on download