Operate with confidence

Maintenance mode is the write freeze. Use it on purpose.

Maintenance mode is the install-wide write freeze for self-hosted urgentry. Use it for upgrades, recovery work, or operator interventions that should stop new writes for a while.

Self-Hosted Mode Deployment Guide
Write freezeThis is the install-wide stop sign for new writes.
Use it for upgradesOr recovery work, or any intervention where you need the system to stay still.
Binary commandsThe core control plane exposes maintenance mode directly.
Compose wrapperThe packaged stack exposes the same operations through ops.sh.
Binary commands

Use the control plane directly.

maintenance commands 
./urgentry self-hosted maintenance-status --control-dsn "$URGENTRY_CONTROL_DATABASE_URL"
./urgentry self-hosted enter-maintenance --control-dsn "$URGENTRY_CONTROL_DATABASE_URL" --reason "upgrade window"
./urgentry self-hosted leave-maintenance --control-dsn "$URGENTRY_CONTROL_DATABASE_URL"
Compose wrapper

Use the same path through the packaged stack.

ops.sh 
bash deploy/compose/ops.sh maintenance-status
bash deploy/compose/ops.sh enter-maintenance "upgrade window"
bash deploy/compose/ops.sh leave-maintenance
Validation

Leave maintenance mode and prove the stack is alive again.

smoke after maintenance 
bash deploy/compose/smoke.sh up

What to check

  • The stack takes writes again
  • The smoke path passes
  • The reason you froze writes is actually resolved

Next docs

Go back to the deployment guide if you are still staging the rollout, or check the HA baseline if you are validating the operator posture.

Deployment Guide HA Baseline Self-Hosted Mode