Overview
Running an eetr-auth deployment day to day — secrets, maintenance, upgrades, and teardown.
Once deployed, eetr-auth needs the usual operational care: keeping secrets and signing keys
consistent, letting scheduled maintenance run, applying upgrades, and tearing down cleanly when
needed.
Secrets & key rotation
The secrets the server needs, how JWT signing keys and the published JWKS stay consistent, and how to rotate safely.
Maintenance & monitoring
The daily cleanup cron, the verify checks, and observability.
Upgrades
Apply new schema patches and redeploy while preserving secrets.
Teardown
Empty R2 and destroy the infrastructure without leaving orphans.
Recurring safety net
npm run verify (local) and npm run verify:remote (deployed) re-check that the JWT signing key,
the published JWKS, the seeded OIDC scopes, and the required secrets are all consistent. Run
verify:remote after any key rotation or schema migration.