docs(config): explain that in-app settings persist across a compose restart
Runtime overrides (global app_setting.runtime_config + per-tenant tenant_retention)
live in the opngms_pg volume, so a restart / down+up / image upgrade does NOT reset
them to defaults; only 'down -v' (destroying the volume) does.
docs: audit log viewer (v0.10.0) + per-tenant retention (v0.11.0)
Audit section in Security (viewer + CI guard + non-RLS code-gate); retention knobs
in Configuration; per-tenant indices + worker-owned retention in Log-Lake; the
report<->retention guard in Reporting; Home capability rows.
docs: Security/Perimeter feature + tunables + refreshed screenshots; perimeter report sections toggled with the others (not per-device)
docs: add Screenshots page; accurate MASTER_KEY rotation (all 5 encrypted columns); mark editor 3c shipped
docs: comprehensive OPNGMS wiki (install, architecture, config, editor, log lake, security, reporting, ops)
Add the full operator + contributor manual as 12 wiki pages, every claim
grounded in the repository:
- Home / _Sidebar — overview and persistent navigation
- Installation — prerequisites, four TLS models, pull & start, first run
- Architecture — component diagram, services, data flows, RLS multi-tenancy
- Configuration — complete environment-variable reference
- Upgrading — pull+up flow, version pinning, backups, MASTER_KEY rotation
- Configuration-Editor — the version-aware editor & catalog pipeline (3a/3b
built; 3c diff/config.xml-map fenced as planned/not-built)
- Log-Lake — the optional mTLS syslog to OpenSearch lake
- Reporting — SMTP delivery, per-tenant settings, schedules
- Security — RLS, encrypted-at-rest secrets, MFA, CI scans, hardening
- Troubleshooting — grouped symptom to cause to fix
- Development — local dev, tests, CI, contribution flow
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>