Per-module functional reference. Each file describes what a module does, the
HTTP routes it owns, the database tables it owns, and how its features are
configured. For how to add a module or how the module system works in
general, see ../develop/module/.
These ship with the template and are owned by upstream — keep them in sync
when you merge from upstream. See
../develop/forking.md § "Template surface vs your
application".
| Module | Page |
|---|---|
account (users, auth, groups, TOTP, single-user mode) |
account.md |
audit (event log + retention sweep) |
audit.md |
backup (export / restore + DEK proof) |
backup.md |
cron (scheduler + action registry) |
cron.md |
encryption (ECIES at-rest, master/dek, unlock) |
encryption.md |
file (storage drivers + ref-counted GC) |
file.md |
item (base composition row + comments + attachments) |
item.md |
policy (Zanzibar tuples + access rules) |
policy.md |
settings (per-key DB-backed settings + admin UI) |
settings.md |
system (health, version, build info) |
system.md |
The template ships reference business modules that demonstrate composition
on top of item + policy + file. This fork removed them (document and
issue).
| Module | Page |
|---|---|
registry (lode release registry: namespaces, packages, versions and assets, token grants, quotas, admin, read feed) |
registry.md |