Package a recoverable production release #27

New issue

Open

opened 2026-07-14 22:32:31 -04:00 by caleb-brown · 0 comments

caleb-brown commented

2026-07-14 22:32:31 -04:00

Owner

What to build

A Temper Operator can deploy, back up, restore, upgrade, and roll back a supported non-root release using the documented single-site production topology.

Acceptance criteria

The release produces a non-root OCI image with explicit web, worker, and migration commands.
The supported Compose topology includes PostgreSQL, persistent storage, health behavior, resource guidance, and reverse-proxy TLS instructions.
Backup documentation covers PostgreSQL plus separately protected encryption keys and includes a verification procedure.
A restore drill reconstructs a working Deployment and verifies encrypted credentials, Operator access, repository state, and review history.
Upgrade and rollback procedures require appropriate backups, check schema compatibility, and never run migrations implicitly from web startup.
Fresh-install and supported-prior-version upgrade tests exercise the exact released artifacts.
The documented support limits exclude multi-region active-active operation, zero-downtime schema upgrades, and a v1 HA SLA.

Blocked by

#22 — Manage Temper Operators and sessions
#23 — Rotate service credentials and encryption keys
#24 — Pause, disconnect, uninstall, and purge repositories
#25 — Expose operational health and backpressure

## What to build A Temper Operator can deploy, back up, restore, upgrade, and roll back a supported non-root release using the documented single-site production topology. ## Acceptance criteria - [ ] The release produces a non-root OCI image with explicit web, worker, and migration commands. - [ ] The supported Compose topology includes PostgreSQL, persistent storage, health behavior, resource guidance, and reverse-proxy TLS instructions. - [ ] Backup documentation covers PostgreSQL plus separately protected encryption keys and includes a verification procedure. - [ ] A restore drill reconstructs a working Deployment and verifies encrypted credentials, Operator access, repository state, and review history. - [ ] Upgrade and rollback procedures require appropriate backups, check schema compatibility, and never run migrations implicitly from web startup. - [ ] Fresh-install and supported-prior-version upgrade tests exercise the exact released artifacts. - [ ] The documented support limits exclude multi-region active-active operation, zero-downtime schema upgrades, and a v1 HA SLA. ## Blocked by - [#22](https://git.caleb-brown.dev/caleb-brown/temper/issues/22) — Manage Temper Operators and sessions - [#23](https://git.caleb-brown.dev/caleb-brown/temper/issues/23) — Rotate service credentials and encryption keys - [#24](https://git.caleb-brown.dev/caleb-brown/temper/issues/24) — Pause, disconnect, uninstall, and purge repositories - [#25](https://git.caleb-brown.dev/caleb-brown/temper/issues/25) — Expose operational health and backpressure

caleb-brown added the

ready-for-agent

label

2026-07-14 22:32:31 -04:00

caleb-brown referenced this issue

2026-07-14 22:32:32 -04:00

Prove the complete v1 operating envelope #28

caleb-brown added a new dependency

2026-07-14 22:38:31 -04:00

#22 Manage Temper Operators and sessions

caleb-brown added a new dependency

2026-07-14 22:38:32 -04:00