
Show HN: Hookman – One stable webhook URL that follows your preview branch
Hookman sits between your webhook providers and your deployments, so Stripe, Paddle and the rest can keep pointing at the same endpoint.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
Hookman sits between your webhook providers and your deployments, so Stripe, Paddle and the rest can keep pointing at the same endpoint.
Switch branches, add routing rules or send the same event to multiple deployments without touching your provider configuration.
Branch A Branch B Live
Setup
Create an account and project. The project slug becomes part of your permanent Hookman webhook endpoint.
Tell Hookman where each branch is running using the dashboard, CLI or GitHub Action.
hookman register
--branch feature/checkout
--url https://pr-42.myapp.com/api/webhooks/stripe
03 Point your provider at Hookman
Update Stripe or another webhook provider once to use the Hookman endpoint. You then leave it unchanged.
Choose the active deployment from the dashboard or CLI, or automate the process through GitHub.
hookman switch
--project payments
--branch feature/checkout
Webhooks now routed to feature/checkout
< #1 Switch routing
“Point a webhook somewhere but let me change it later ”
Pick a deployment, hit activate, done. Every webhook that hits your endpoint goes there until you say otherwise. No dashboard trips to Stripe, no ngrok URL in a Slack thread, no redeploy.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。