justin
8c051778a4
The Windows ZVM is largely deprecated in favor of the ZVMA on Kubernetes, so the older recipe and its companion sender script are gone. The ZVMA recipe is promoted to canonical and its header no longer references the deleted recipe. - delete docs/recipes/zerto-pre-post-scripts.md (Windows-ZVM-only) - delete scripts/examples/zerto-post-failover.ps1 (curl.exe sender) - promote ZVMA recipe in README, docs/README, installation, sync-wiki If anyone still needs the DNS-update / service-check handler from the deleted recipe it's available in git history (commit before this one). Happy to re-resurrect into a generic post-failover recipe if folks ask.
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 ZVMA pre/post → notify + VM health check — 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 ZVMA (Kubernetes) pre/post → notify + VM health check ← canonical use case
- GitHub-style HMAC-signed webhook
- Pop UI on the user's desktop
The Zerto ZVMA recipe ships with zerto-zvma-send.ps1 (sender, runs inside the ZVMA scripts-service container) plus zerto-receiver-notify.ps1 and zerto-receiver-vm-healthcheck.ps1 (receivers, run on the Webhook Server host).