Same fields as the postgres variant: sizes/tables/rows/top tables from
information_schema.TABLES, connections/uptime from SHOW GLOBAL STATUS,
InnoDB buffer-pool hit ratio as cache_hit_pct. Best-effort like the
rest — any failure returns None and never disturbs the heartbeat.
Build and Push backhaul-agent / build (push) Successful in 39s
- sqlite3 in the image so the agent can back up SQLite files (Vaultwarden etc.) via .dump.
- Sync backhaul-agent.py to v1.3: sqlite engine (sqlite:<path> target), chunked upload
(large dumps past the CDN cap), live metrics, self-update UA fix.
Build and Push backhaul-agent / build (push) Successful in 42s
One docker run on a database's private network starts backing it up:
- backhaul-agent.py: stdlib-only sidecar — every-minute check-in, app-owned
dump schedule, streams pg_dump/mysqldump/mongodump home chunked, self-updates.
- entrypoint.sh: bootstraps the newest script, installs the once-a-minute cron
(sources persisted env), runs once immediately, hands off to cron; logs to a
file surfaced via docker logs.
- Dockerfile: debian-slim + pg_dump 17 (PGDG — required for Postgres 17 servers)
+ mysql client. Mongo tools to follow.
- CI builds + pushes the public image and asserts the dump tools are present.