Backups, 1-Click Updates & Editorial Postbox

Standalone Qwiki makes routine maintenance, core upgrades, and cross-team content intake predictable and non-destructive.

Full Backups (tool-backup)

Open admin ▾ ➔ 📦 Backup & Export:

• Scans qwiki.json, users.json, content/, data/ (revisions, trash, talk pages), and uploads/ and shows file counts and total size.
• Click Download Backup to generate a single .zip archive of your entire portal state without shell access.

1-Click Core Updates

When a newer Standalone Qwiki release is published on GitHub:

• An Update Available notice appears in the admin dropdown (admin ▾).
• Clicking it downloads and applies the core application update in one step while preserving your live qwiki.json, users.json, content/, data/, uploads/, and custom assets/extensions/.
• If your installation hosts child sub-wikis, core updates propagate safely without touching each sub-wiki's isolated content or users.

Editorial Postbox & Desktop Transfer (tool-postbox)

The Document Postbox (admin ▾ ➔ 📬 Document Postbox, or Send to Postbox... in the document toolbar) lets teams transfer documents and folders asynchronously between independent Qwiki portals—or straight from a desktop workstation—without overwriting live chapters blindly.

How Postbox Works

1. Sender / Workstation: Either send a chapter from one Qwiki portal to a configured peer Qwiki, or use the built-in zero-dependency Python 3 CLI / OS integration (Send to Qwiki on Linux, Windows, or macOS) to package Markdown files and their local image assets into a Postbox envelope.
2. Staging Inbox: Incoming packages land in the recipient portal's Postbox Inbox rather than modifying content/ directly.
3. Reviewer-Controlled Acceptance: An admin on the destination wiki previews the staged package, maps it to a target category, and clicks Accept (or Reject).