Skip to main content

Database

Jiandu supports two database choices for the same single-process deployment model.

SQLite​

SQLite is the default and the best starting point for one host. Keep its file on persistent local storage, not a network filesystem, and include it in coordinated backups.

Choose SQLite when you want fewer moving parts and do not already operate PostgreSQL.

PostgreSQL​

PostgreSQL 17.x and 18.x are supported for operators who already have a reliable PostgreSQL service and recovery practice. Require encrypted connections, use a dedicated database and role, and protect connection secrets outside the repository.

Choose PostgreSQL because it fits your operations—not because it allows multiple Jiandu application processes. Jiandu still expects one owning process per installation.

Validate before switching​

Database portability is a controlled export-and-restore operation. The destination must be a new explicit path or an empty, unpublished database. Jiandu refuses ambiguous or already-published targets so a retry cannot overwrite a live installation.

Before a planned move:

  1. Stop document changes.
  2. Create and verify a fresh backup.
  3. Run the portability preflight and address missing client tools or version mismatches.
  4. Restore into a new target.
  5. Verify counts, access rules, search, and representative original files.
  6. Publish the new target only after verification.

See database migration for the operator workflow.