zeekay aad4fbc516 docs(self-hosting): describe the SQLite/Base storage this actually uses ...

The self-hosting docs still described PostgreSQL — connection strings, database
pricing, "plan for database growth". esign runs on embedded SQLite (Hanzo Base),
a single sign.db file on a persistent volume, so every one of those instructions
sent a self-hoster to provision infrastructure the app never touches.

Rewrites configuration, deployment, getting-started and maintenance to match:
documents stored base64 in sign.db rather than in Postgres, capacity planning
against the volume holding that file rather than database pricing, and backups
of the file rather than pg_dump.

Docs only — no behaviour change.

2026-07-26 02:07:33 -07:00

..

docs

docs(self-hosting): describe the SQLite/Base storage this actually uses

2026-07-26 02:07:33 -07:00

openpage-api

rename: @hanzo/sign-* → @hanzo/esign-* (full eSign brand consistency)

2026-06-21 19:56:09 -07:00

remix

fix(server): bundle the esign ZAP server layer + resilient migrate

2026-06-22 02:56:25 -07:00