You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Write an operator deployment and rollback runbook #60
Implemented in livepeer/node#14 (commit 9a351d4). The requested guidance is covered by the existing operator guides, with copyable commands added where useful:
Installation: versioned Linux binary bundles, archive and executable checksum verification, and PATH setup.
Configuration and secrets: config precedence, credential files and keystores, destination grants, persistent storage, and health/metrics probes.
Orchestrator operation: startup, private destination grants, public URLs/TLS termination, and paid-mode configuration. Ethereum RPC connections explicitly do not require destination grants.
Signer operation: startup, payment configuration, accounting, and monitoring.
Payment recovery: live SQLite backup and integrity-check commands, upgrade/rollback examples, migration compatibility checks, and preservation of current redemption/accounting state.
Service supervision and TLS provisioning remain deployment-specific. These guides provide the shared requirements and commands without adding a separate runbook.
Verified release checksums/extraction, backups containing committed WAL data for both database types, rejection of an unknown migration before startup, and local forwarding, readiness/metrics, and graceful shutdown. Documentation links and snippet syntax also passed. The cleanup reduced overall documentation word count by 14%.
Activity
j0sh commentedon Oct 23, 2026
Implemented in livepeer/node#14 (commit 9a351d4). The requested guidance is covered by the existing operator guides, with copyable commands added where useful:
Service supervision and TLS provisioning remain deployment-specific. These guides provide the shared requirements and commands without adding a separate runbook.
Verified release checksums/extraction, backups containing committed WAL data for both database types, rejection of an unknown migration before startup, and local forwarding, readiness/metrics, and graceful shutdown. Documentation links and snippet syntax also passed. The cleanup reduced overall documentation word count by 14%.
Closing as completed.