Preserve the private database endpoint and publish live deployment receipts #8
Loading…
Reference in a new issue
No description provided.
Delete branch "ops/portal-runtime-receipts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The shared Coolify proxy network contains an unrelated
postgresalias, so the API needs this deployment's unique private database hostname. Preserve the independently reviewed host-only runtime hook on every release, with the same protected password, project/volumes and trust settings. The release helper reuses a tested immutable image, verifies command readback and the platform's command-length limit, and fails if the pinned hook download fails.Publishes sanitized exact-image storage and live receipts: workload
e44569e45b15dbee4b0347dff742f92bd85bedb2, immutable manifestsha256:07b476118ac7ca8a8af9653471026d02c0e615ace174231bd50aea06392b607e, separately pinned ops hookb8aa303154b25d3017816c258b0daeb8954b7b26, migrations 1–5, 13 storage/restore assertions and 16 live owned-wallet checks. Current workload/image are unchanged. Helper syntax/help and worst-case command length checked; independent source/live review is recorded.Issue #4 stays open: off-host encrypted backup and key-recovery proof remain agent-owned continuation. Provider enrollment/delivery and verified contract deployments remain gated and owned separately. No real-recipient messages or chain transactions were sent.