Operations¶
How to run hookspool on a host, keep it healthy and fix what goes wrong. Nothing here needs the source code.
| page | what is in it |
|---|---|
| Running | installing on a host with systemd and a reverse proxy, and moving senders over one at a time with a rollback for each |
| Health and repair | telling that it is healthy, issues and alerts, stuck batches, retention, backup and restore |
| Sweeps | which senders retry, what keeps the rest honest, and the known limits |
| Drills | the gateway-down drill |
| Upgrading | moving a running install to a new version |
| Day-two commands | the commands you reach for once it is running |
| CLI reference | every command, option, environment variable and exit code |
| Releasing | cutting a release: the version, the tag, the GitHub Release and PyPI, and the one-time setup |
The files these pages talk about (systemd units, an nginx example, a complete config and the GitHub redelivery sweep) are in
deploy/.