/var/lib/leamout/deployment.json. Treat that identity, generated environment secrets, durable application state, installed license material, TLS material, and recording storage as separate recovery concerns.
The current leamout backup command protects deployment identity/configuration, durable application state, and installed offline license/keyring material. It does not currently include recording media or TLS certificates.
A recovery plan should therefore maintain protected copies of:
- Leamout CLI/runtime release artifacts needed for the intended version.
- A recent
leamout backuparchive. - TLS certificate/private-key material and any carrier CA bundles.
- Recording storage when recordings must survive host loss.
leamout doctor, confirm service health, then validate signaling/media before admitting production traffic.