WikiDeck/wikideck
3
0
Fork 1
Code Issues 8 Pull Requests Actions Packages Projects 2 Releases Wiki Activity

Persistent PostgreSQL sandbox deployment

Browse Source
This commit is contained in:
eric
2026-10-20 16:02:18 -04:00
parent 84a505c4a5
commit 4cac26d84b
14 changed files with 333 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/postgres-financial-storage.md
+2
View File
@@ -47,6 +47,8 @@ The operator CLI is [scripts/custody-db.ts](../scripts/custody-db.ts), available
The CLI is included in the runtime image. No existing deployment, database secret or fund wallet was changed automatically by this implementation.
**Persistent local deployment now available:** [deployment guide](persistent-custody-sandbox.md) and [standalone Compose stack](../compose.custody.yaml) provision isolated named volumes, scoped generated credentials, verified PostgreSQL TLS/SCRAM, separate roles and a one-shot migration service. Recreated containers retained a signed fictitious credit and custodian identity in rehearsal. This explicitly started a new sandbox, not a cutover of existing node data or a live-custody deployment; production backup, certificate rotation and activation gates remain open.
## Explicit SQLite cutover and rollback limits
[Importer](../server/market/custody-import.ts) is bounded to the existing sandbox source size (128 MiB), not a general live-money migration utility. The CLI takes the same exclusive stopped-node directory lock as node startup. Calling the underlying library assumes the caller has already stopped all source writers.