Launch offerYour first 90 days of BYOC are free for one server — connect a server you already rent. Until January 15, 2027.Claim it →

Auto-Deploy & Deploy Modes

Deploy modes (auto, review-a-diff, pinned revision), automatic branch checks on any Git host, and instant deploys with an optional GitHub webhook.

Once your App is pointed at a Git repository, every push to its branch can deploy automatically — no more clicking Deploy by hand after each change. For most apps there is nothing to set up: it's on by default.

Deploy modes

Every Git-based App has a deploy mode, which decides how new commits become deploys. Change it from the App's Settings page; the Overview page shows the current mode and revision.

ModeWhat happens on a new commitUse it when
Auto Deploy (default)Raklane deploys it automatically.You want every push to the branch to go live.
Manual Deploy with DiffNothing, until you act. The Overview shows when your app is behind the branch; review the diff, then deploy exactly the commit you reviewed.You want a human to look at changes before they go out.
Deploy by Git RevisionNothing. Deploys always use the commit, tag, or branch you pinned.You want to hold an app on a specific release.

In the two manual modes, a push never deploys anything on its own — not even with a webhook set up.

How Auto Deploy finds new commits

In Auto Deploy mode, Raklane notices new commits in two ways:

  • Automatic checks (any Git host, no setup). Raklane regularly checks your App's branch for new commits and deploys each new one it finds. This works for GitHub, GitLab, Bitbucket, and any other Git host. The App's Settings page shows how often the branch is checked and what the last check found.
  • A GitHub webhook (optional, instant). GitHub tells Raklane about a push the moment it happens, so the deploy starts within seconds instead of at the next check. Set it up only if you want that speed — see below.

Auto-deploy starts after your App's first deploy. That first deploy is always one you start yourself, so you choose where it runs and with what resources; every automatic deploy after it reuses those choices.

Checking that it's working

Open your App's Settings page. With Auto Deploy selected, the Automatic checks panel shows the latest result:

You seeWhat it means
Up to date with abc1234The latest deploy already runs the newest commit on the branch.
New commit abc1234 found — deployingA deploy just started. Follow it on the Status page (see Logs & Status).
Starts after this app's first deployDeploy the App once; later commits are then picked up automatically.
The app is pausedPaused apps are never deployed automatically. Resume the App to continue.
Couldn't check the branchRaklane couldn't read your repository — the message says why. For a private repository this usually means its access token has expired or been revoked; see Secrets → Private repositories. Raklane keeps retrying, less often while the problem lasts.

Make it instant with a GitHub webhook

This part is optional. Everything is done from your App's Settings page, which shows the values to copy into GitHub.

1. Generate a signing secret

The secret is shared between Raklane and GitHub, so Raklane can confirm each push notification really came from GitHub.

  1. Open your App's Settings page and select Auto Deploy (save it, if it wasn't already selected).
  2. In the Instant deploys with a GitHub webhook panel, click Generate secret.
  3. Copy the secret that appears. Raklane stores it encrypted and never shows it again. If you lose it, generate a new one and update GitHub.

Already have a webhook_secret from your Organization's Secrets page? Choose Use an existing secret instead.

2. Add the webhook on GitHub

In your GitHub repository, go to Settings → Webhooks → Add webhook. The Settings page links straight there. Fill in:

GitHub fieldValue
Payload URLhttps://api.raklane.com/v1/webhooks/github — the same for every App, and also shown with a copy button on the Settings page.
Content typeapplication/json
SecretThe secret you copied in step 1.
Which events would you like to trigger this webhook?Just the push event.

Leave SSL verification enabled and Active checked, then click Add webhook.

You don't need to tell Raklane which App the webhook belongs to. Raklane matches each push by its repository and branch, then checks the signature against that App's secret.

3. Check that it works

GitHub sends a test ping right away. Open the webhook's Recent Deliveries tab — the ping should have a green check. Then push a commit to your App's branch: a deploy starts within a few seconds.

On a push delivery, a red 401 means the secret on GitHub doesn't match the one saved in Raklane. Generate a new secret and paste it into the webhook's settings on GitHub.

Notes

  • Auto-deploy only works for Git-based sources, not archive uploads.
  • Pushes to branches other than your App's branch are ignored.
  • For the webhook, your App's repository URL must be written the way GitHub sends it: https://github.com/owner/repo.git, https://github.com/owner/repo, or git@github.com:owner/repo.git. The Settings page warns you if it isn't. The automatic checks work either way.
  • Turning off the webhook (Turn off webhook on the Settings page) leaves the automatic checks running. To stop automatic deploys entirely, switch to one of the manual modes.
  • Something not working? See Troubleshooting.