Operations

Data and backups

Contents of the persistent volume and a consistent backup procedure.

Contents of data/

data/
├── tradoc.db
├── tradoc.db-wal
├── tradoc.db-shm
├── provider_credentials.json
├── glossaries/
├── jobs/<id>/input/
├── jobs/<id>/output/
└── tmp/

The -wal and -shm files may exist while SQLite is active. Do not copy only tradoc.db while the application is writing.

  1. Pause active projects.
  2. Stop TraDoc or its container cleanly.
  3. Back up the entire data/ directory with its permissions.
  4. Restart the application.
  5. Test restoration periodically in an isolated directory.

Data to protect

The volume can contain manuscripts, translations, glossaries and provider keys. Encrypt off-site backups and restrict their access.

Restoration

Restore a consistent version of the whole volume before starting TraDoc. Then check /health, the project list, a glossary and a known export.

Security

Authentication, origins, LLM endpoints, import limits, network exposure and private reporting.

Updating

Back up data, record the running image, then pull or rebuild without losing projects.