webhooker

163 Commits 10 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
clawbot	ef8e8cf398	Serve /metrics from a registry of its own (closes #227 ) check / check (push) Successful in 4m2s Details The HTTP metrics recorder, the delivery collectors and the Go and process collectors now register on one prometheus.Registry that fx provides, instead of Prometheus's global default registry, and /metrics serves that registry. A second metrics-enabled router in one process, or the server tests run with -count=2, no longer panics on a duplicate registration. The middleware builds its recorder once, in New, so installing Metrics() on more than one router over the same graph is also safe. The scrape keeps the same series and labels, including go_, process_ and promhttp_metric_handler_*. Model: opus-5-5	2026-09-29 09:20:29 +00:00
clawbot	03cd1859d7	Add an egress CIDR allowlist to the SSRF guard (closes #204 ) (#217 ) check / check (push) Successful in 3m1s Details	2026-08-20 10:34:42 +02:00
clawbot	9969694a47	Add a webhooker resetpw subcommand and a bootstrap banner (closes #208 ) (#239 ) check / check (push) Successful in 3m25s Details The admin bootstrap password was printed once, as one line among roughly 45 fx lines, and under docker run -d went to container logs subject to rotation. There was no reset path at all -- no subcommand, no forgot-password flow, no env override -- so recovery meant hand-deleting the users row from webhooker.db, which was documented nowhere. Adds webhooker resetpw [-generate] <username>. The password is read from stdin or generated with the existing crypto/rand helper, never taken from argv where /proc would publish it. It reuses the existing Argon2id hashing rather than reimplementing the parameters, and writes a single UPDATE only after the hash is complete, so no failure can leave an account with no usable password. An unknown username is a hard error and never creates an account. It refuses to run against a DATA_DIR held by a live instance, via the exclusive lock from #201. DATA_DIR and webhooker.db are checked to exist before the lock is acquired, so a mistyped path creates nothing -- neither a directory tree nor a stray lock file. The bootstrap password now appears exactly once, in a distinct banner written straight to a caller-named writer rather than as an fx log line.	2026-08-20 08:01:42 +02:00

Author

SHA1

Message

Date

clawbot

ef8e8cf398

Serve /metrics from a registry of its own (closes #227 )

check / check (push) Successful in 4m2s

Details

The HTTP metrics recorder, the delivery collectors and the Go and
process collectors now register on one prometheus.Registry that fx
provides, instead of Prometheus's global default registry, and
/metrics serves that registry. A second metrics-enabled router in one
process, or the server tests run with -count=2, no longer panics on a
duplicate registration.

The middleware builds its recorder once, in New, so installing
Metrics() on more than one router over the same graph is also safe.
The scrape keeps the same series and labels, including go_*,
process_* and promhttp_metric_handler_*.

Model: opus-5-5

2026-09-29 09:20:29 +00:00

clawbot

03cd1859d7

Add an egress CIDR allowlist to the SSRF guard (closes #204 ) (#217 )

check / check (push) Successful in 3m1s

Details

2026-08-20 10:34:42 +02:00

clawbot

9969694a47

Add a webhooker resetpw subcommand and a bootstrap banner (closes #208 ) (#239 )

check / check (push) Successful in 3m25s

Details

The admin bootstrap password was printed once, as one line among roughly
45 fx lines, and under docker run -d went to container logs subject to
rotation. There was no reset path at all -- no subcommand, no forgot-password
flow, no env override -- so recovery meant hand-deleting the users row from
webhooker.db, which was documented nowhere.

Adds webhooker resetpw [-generate] &lt;username&gt;. The password is read from
stdin or generated with the existing crypto/rand helper, never taken from
argv where /proc would publish it. It reuses the existing Argon2id hashing
rather than reimplementing the parameters, and writes a single UPDATE only
after the hash is complete, so no failure can leave an account with no
usable password. An unknown username is a hard error and never creates an
account.

It refuses to run against a DATA_DIR held by a live instance, via the
exclusive lock from #201. DATA_DIR and webhooker.db are checked to exist
before the lock is acquired, so a mistyped path creates nothing -- neither
a directory tree nor a stray lock file.

The bootstrap password now appears exactly once, in a distinct banner
written straight to a caller-named writer rather than as an fx log line.

2026-08-20 08:01:42 +02:00