webhooker

245 Commits 4 Branches 0 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
sneak	92dbfc8996	Event log: show attempt and delivery times, label replays, zone event times (closes #386 ) check / check (push) Successful in 3m19s Details Each attempt shows when it was recorded and each delivery when it was created, in the event log and on the event's page. The event log's event times read as the recent events list does: how long ago, with the full UTC time on hover. A delivery records whether Replay created it, in a new replay column added to the delivery model in place. Such a delivery is labelled a replay in the event's summary line and in both pages' delivery lists. Model: opus-5-5	2026-10-03 00:52:03 +00:00
clawbot	bcdd4791ec	Say what a database or log target's attempt did, without a status (closes #388 ) check / check (push) Successful in 3m14s Details In the event log and on an event's page, every attempt by a `database` or `log` target read "success Status: — (no response)". Those targets make no HTTP request, so there is no response to have, and "no response" reads like a failed connection, which is what it means for an `http` target. A successful `database` attempt now reads "archived" and a successful `log` attempt "written to the log", with no status shown; a failed one keeps "failure" and its error line, also with no status. `http` and `slack` attempts are unchanged. The change is in the one shared attempt template. Model: opus-5-5	2026-10-03 02:41:17 +02:00
clawbot	719d7013ee	Give each event its own page and show bodies the same everywhere (closes #369 ) check / check (push) Successful in 3m17s Details Each event now has its own page at /hook/ID/events/EVENTID, behind the login, showing its details, its whole body and every delivery; a resubmitted copy links to its original's page. The recent events on the webhook page link there and expand to show their bodies, only the newest expanded on load. One renderer and one template show a body the same way in the recent events, the event log and the event's page: whole up to 32 KiB, cut there in the two lists with links to the event's page and the download; JSON pretty-printed unless that would grow it past four times plus 1 KiB; over 200 lines in a scrolling box; a body holding NUL or control characters treated as binary and never dumped raw. Model: opus-5-5	2026-10-02 22:00:42 +02:00

Author

SHA1

Message

Date

sneak

92dbfc8996

Event log: show attempt and delivery times, label replays, zone event times (closes #386 )

check / check (push) Successful in 3m19s

Details

Each attempt shows when it was recorded and each delivery when it was
created, in the event log and on the event's page. The event log's
event times read as the recent events list does: how long ago, with
the full UTC time on hover.

A delivery records whether Replay created it, in a new replay column
added to the delivery model in place. Such a delivery is labelled a
replay in the event's summary line and in both pages' delivery lists.

Model: opus-5-5

2026-10-03 00:52:03 +00:00

clawbot

bcdd4791ec

Say what a database or log target's attempt did, without a status (closes #388 )

check / check (push) Successful in 3m14s

Details

In the event log and on an event's page, every attempt by a `database` or `log` target read "success  Status: — (no response)". Those targets make no HTTP request, so there is no response to have, and "no response" reads like a failed connection, which is what it means for an `http` target. A successful `database` attempt now reads "archived" and a successful `log` attempt "written to the log", with no status shown; a failed one keeps "failure" and its error line, also with no status. `http` and `slack` attempts are unchanged. The change is in the one shared attempt template.

Model: opus-5-5

2026-10-03 02:41:17 +02:00

clawbot

719d7013ee

Give each event its own page and show bodies the same everywhere (closes #369 )

check / check (push) Successful in 3m17s

Details

Each event now has its own page at /hook/ID/events/EVENTID, behind the login, showing its details, its whole body and every delivery; a resubmitted copy links to its original's page. The recent events on the webhook page link there and expand to show their bodies, only the newest expanded on load. One renderer and one template show a body the same way in the recent events, the event log and the event's page: whole up to 32 KiB, cut there in the two lists with links to the event's page and the download; JSON pretty-printed unless that would grow it past four times plus 1 KiB; over 200 lines in a scrolling box; a body holding NUL or control characters treated as binary and never dumped raw.

Model: opus-5-5

2026-10-02 22:00:42 +02:00