Guides
Publishing
Live content, build hooks, GitHub Actions, Coolify.
| Mode | For | What Publish does |
|---|---|---|
| Live content | Sites that fetch WordPress at request time (SSR, ISR) | Nothing to publish: saving is enough, the button is hidden |
| Build hook | Vercel, Netlify, Cloudflare Pages, any rebuild URL | POSTs to the hook |
| GitHub Actions | Static builds run in Actions | Dispatches a workflow and follows the run live |
| GitHub commit | Hosts that deploy on every push | Pushes an empty commit to the branch |
| Coolify | Self-hosted Coolify | Calls the deployment webhook |
Tokens are encrypted in the database with a key derived from your WordPress salts. GitHub settings are checked when saved: repository, branch, workflow and token expiry.
Publishing can also be automatic: tick Publish on its own after each change and Leiho deploys once the edits stop (60 s by default), changes made in wp-admin included. Nothing to set up on the server: the editor shows a discreet countdown and publishes when it runs out, or right away if the client closes the tab; any open wp-admin tab publishes through the Heartbeat once the delay has passed; WP-Cron is the fallback when nobody is logged in. Whatever fires first, one batch of changes gives one deployment, and a build already running or the minimum delay between deployments only postpones it.