85a700841b
CI / build (pull_request) Has been cancelled
Squashes the work that landed on GitHub via PRs #2 (v0.1.1), #3 (v0.1.2), and #4 (wiki sync) into a single commit on Gitea so both remotes converge. Content is identical to github/main; commit history is split for branching reasons (Gitea was merged via PR #1 long ago, GitHub used squash merges from then on, so the SHAs diverged). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Webhook Server documentation
Webhook Server is a Windows service that runs a script (PowerShell, cmd, or any executable) when an HTTP request hits a URL you choose. It's designed for sysadmins who want to wire a tool like Zerto pre/post scripts, GitHub Actions, a monitoring system, or a backup tool into a Windows-side automation step — without writing a custom listener every time.
New here? Start with these
- Concepts — five-minute read on what a webhook is and how this server uses one
- Installation — download, install, first endpoint
- Recipe: Zerto failover post-script → DNS + service checks — the canonical reason this exists
Topical
- Upgrading
- Uninstalling
- Run As modes — when to use which
- Service account & Active Directory
- Network & security
- Troubleshooting
Recipes (cookbook style)
- Zerto failover post-script → DNS + service checks ← canonical use case
- GitHub-style HMAC-signed webhook
- Pop UI on the user's desktop
The flagship Zerto recipe also ships with a ready-to-use Zerto-side post-script at scripts/examples/zerto-post-failover.ps1.