https://aftermarket.dev/tags/afterhook/ Recent content in afterhook on Aftermarket.dev Hugo -- gohugo.io en-us Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/afterhook-released-to-send-webhooks-from-software-that-never-had-any/ Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/afterhook-released-to-send-webhooks-from-software-that-never-had-any/ Aftermarket 0.5.0 adds AfterHook, run as aftermarket hook. It’s for the app that changes data and never tells anyone. You know the kind. An order system writes its status to a file. A vendor tool drops CSV exports into a folder at odd hours. A small internal app keeps everything in SQLite and has no API at all. Something else needs to know when those things change, and the usual answer is a cron job someone wrote years ago that diffs a file and sends an email. https://aftermarket.dev/case-study-getting-webhooks-from-an-old-app-with-afterhook/ Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/case-study-getting-webhooks-from-an-old-app-with-afterhook/ This case uses the examples/legacy-app folder that ships in every download archive, a stand-in for a real old app, so you can run each step yourself. The commands and output below come from a real run of the downloaded aftermarket 0.5.1. The only extras are the sqlite3 program and Go for the receiver. The situation A small order app has been running for years. It writes the current order to status. https://aftermarket.dev/how-afterhook-was-tested-to-turn-every-change-into-one-event/ Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/how-afterhook-was-tested-to-turn-every-change-into-one-event/ AfterHook makes four promises. Every change gives exactly one event. Nothing is lost while the receiver is down or across restarts. A source that didn’t change by meaning sends nothing. And a half-written file is never reported. The tests go after each one, with a fake clock so a test can jump past retry waits without sleeping through them. One change, one event A random test makes 200 edits to a JSON file.