Ship
Deploy hooks and CI
Deploy with a single POST request, and ship only after GitHub checks pass.
Deploy hook
A deploy hook is a secret URL: sending a POST to it deploys the branch the service tracks. Useful for calling after CI finishes, from an external system, or by hand.
- In the service settings, create a hook under Deploy hook.
- The URL is shown only once — save it in your CI secrets.
curl -X POST https://livops.uz/api/hooks/deploy/dh_xxx
- Tokens start with
dh_. Livops stores only their hash. - Recreating a hook revokes the old one.
- A wrong token returns
404; each hook is rate limited. - Hooks can be created, viewed and deleted only from the cabinet (not with an API token).
GitHub Actions example
name: deploy
on:
push:
branches: [main]
jobs:
test-and-deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm ci && npm test
- run: curl -fsS -X POST "${{ secrets.LIVOPS_DEPLOY_HOOK }}"
Deploy after CI passes
On a service connected from GitHub, turn on Deploy after CI passes. Then:
- a push isn’t built right away — the deploy waits in the Waiting for CI state;
- when that exact commit’s GitHub checks pass, the deploy starts;
- if a check fails, is cancelled or times out, nothing is built and the old version keeps running;
- a new push replaces the one that’s waiting.
This setting works only for GitHub repository services, because the result comes through the GitHub App.
Webhooks (outgoing)
Add a webhook under the team’s Settings → Webhooks (/<team>/settings/webhooks), and a JSON POST is sent to the HTTPS URL you specify when a deploy goes live, fails, or an app stops. The body is signed with HMAC-SHA256 in the X-Livops-Signature header. If delivery fails, it retries after 10 seconds, 1 minute and 5 minutes.
Slack and Discord
If the address is a Slack incoming webhook (https://hooks.slack.com/services/...) or a Discord webhook (https://discord.com/api/webhooks/...), that chat’s own message is sent instead of JSON: for example “✅ shop — new version is out” with a link to the site and to the project’s page in the cabinet, or “❌ shop — did not go out” with the reason. The message is written in the team owner’s language (as Telegram messages are), Uzbek if none is set. There is no format to pick: it is read from the address, and the form shows a Slack/Discord badge. Retries work the same way.