1.2.4
Added
- Configuration errors now send a notification card through
NOTIFY_WEBHOOK_URLbefore the container exits. The fail-fast checks added in 1.2.3 were diagnosable but silent —notify_teamswas only reachable from a backup run, so a mistypedTOKENwas only found by someone looking at the container. - The smoke test runs a real HTTP receiver and asserts that both a configuration error and a failed run post a card. Now 15 checks.
Changed
- Behaviour change: an unusable configuration exits
78(EX_CONFIG) instead of1, so monitoring can tell "misconfigured" from "crashed" without parsing logs. Exit codes are documented in the README. TIME_ZONEis validated and applied before the other checks, so every notification carries local time.
Fixed
- Important: the webhook call is backgrounded and waited on, like the daily sleep. A POSIX trap only runs once the foreground command returns, so a
SIGTERMarriving mid-notification used to sit out the stop grace and end inSIGKILL. Measured against an unreachable webhook under the default 10s grace: exit137before, exit143within a second after. - An
INT/TERMtrap is installed before anything can block, and the notification attempt is bounded (10s for configuration errors, 60s for run notifications). - The token file is written with
printfrather thanecho. ci/smoke-test.shno longer reports success when a container fails to complete a cycle within the timeout.
Images
ghcr.io/wus-technik/github-backup-docker:1.2.4 — also published as :stable (linux/amd64, linux/arm/v7, linux/arm64).