Skip to main content

Roll out Jiandu to your household

A dependable archive is a shared habit backed by recovery evidence. Roll Jiandu out in stages so each new source, person, and trust boundary has one clear test.

Stage 1: prove the private local workflow​

Run Jiandu on loopback or with the local Compose example. Claim it with a named human Administrator, store the Owner token offline, and complete the document workflow with samples.

Do not import the archive yet. First decide whether the scope and readiness boundaries match your needs.

Stage 2: prove recovery​

Choose persistent database and blob locations, create a complete backup, and restore it into a new isolated destination. For the promoted Compose topology, run the executable PostgreSQL drill. Open several shared sample originals from the restored copy.

Write down the exact version, locations, commands, and person responsible for the next drill. Keep that runbook outside Jiandu.

Stage 3: add household access​

Choose a stable HTTPS origin and put a reviewed reverse proxy in front of the private backend. Test sign-in and original download from a second device before inviting everyone.

Create named accounts rather than sharing credentials. Give ordinary users Member access; keep administration limited to people who operate the service. Demonstrate how to add, correct, search, and download one sample's preserved original.

Now create a non-sensitive restricted sample and run the two-account restriction drill. Add that restricted sample to the next recovery drill after the accounts and grants exist.

Stage 4: migrate a small, representative set​

Bring in documents from several sources and years. Include awkward examples: an image-only scan, a multi-page PDF, a duplicate, a restricted record, and a file with an unhelpful name.

Reconcile source and destination counts, inspect exceptions, and keep the source archive read-only. If moving from Paperless-ngx, use the reviewed migration guide rather than assuming drop-in compatibility.

Stage 5: add automation one boundary at a time​

Only after the manual workflow is dependable should you add a watched folder, scanner, email connector, external identity provider, remote blob store, telemetry exporter, or plugin. For each one:

  1. document its credential and network boundary;
  2. test a successful item;
  3. test an interruption or invalid item;
  4. confirm the source remains recoverable; and
  5. add the integration to backup and incident procedures.

Definition of ready​

Jiandu is ready for your household when another person—not only the installer—can find and open a document, an operator can restore the installation without touching the live copy, and everyone knows how to report a failure without exposing a secret.

The deployment checklist provides a compact version of these gates.

Last updated on