Guides

Walkthroughs you can follow with a terminal open. Getting traffic to your laptop, keeping generated clients in step, and the setup steps nobody documents until they bite.

04 articles
A branching diagram on black. A provider cloud feeds one indigo box, event evt_a1b2, which splits into four numbered branches. Retry sends two arrows to the same box marked your API, the second annotated attempt 2. Fan-out sends one arrow each to API and billing. Replay sends a dashed arrow labelled forward_type: REPLAY. Two events shows a second box, evt_c3d4, alongside the first. Down the right edge in coral, where each one is repaired: your handler, your topology, nothing, your dedupe key. Under a dashed line: an event is not a delivery.GuidesDuplicate webhooks: four causes, and idempotency fixes oneThe same charge lands twice and the reflex is to reach for idempotency. Four different situations look identical from inside your handler, and they are fixed in four different places.Quentin Mousset4 min readA balance scale. The raised left pan carries a stack of five cards labelled virtualized list, live tail, attempt chain, JSON viewer and replay button, annotated in coral as weeks of work. The lowered right pan carries a single line reading npx shadcn add @repost/delivery-history-table, with a check mark and the note one command. Under the scale, a dashed line and the sentence: the only part worth writing is the token endpoint.GuidesDon't build the webhook delivery table. Install it.A customer asks whether their webhook went out, and two weeks later you are speccing a deliveries page. Repost publishes that page as a shadcn registry.Quentin Mousset4 min readThree test runs on one time axis marked 0s, 0.4s, 5s and 9s. The first, sleep 5, runs the full five seconds although the webhook lands at 0.4s, and the stretch after it is hatched and labelled 4.6s of nothing. The second, sleep 5 on a slow day, ends at 5s with a coral cross reading expected 1, got 0, while the webhook only lands at 9s, too late. The third, repost expect, stops at 0.4s with a check mark reading returns on arrival, and a dashed line continues to a coral bracket: or exit 7 at the timeout.GuidesYour test is sleeping. The webhook already arrived.A sleep is a guess about someone else's latency. Wait for the request itself: the test returns the moment the webhook lands, and fails loudly when it never does.Quentin Mousset3 min readTwo delivery paths compared while a laptop is closed: an ephemeral tunnel URL loses the three events that arrive in that window, with nothing left to replay, while a durable bucket stores all three and streams the backlog down to the laptop on the next repost forward.GuidesForwarding webhooks to localhost without a tunnelPublic tunnels leak URLs, rotate hostnames, and expire mid-debug. Forwarding from a durable bucket keeps the endpoint stable and the payloads replayable.Quentin Mousset6 min read