Automatic deployments

Automatic deployments let Launchdeck deploy your application whenever you push changes to your connected Git repository.

Once enabled, Launchdeck listens for pushes from GitHub or Bitbucket and automatically starts a new deployment.

Enabling automatic deployments

Open your project in Launchdeck and enable automatic deployments for the server you want to deploy to.

Once enabled, pushes to your connected repository can automatically trigger a new deployment.

How automatic deployments work

When Launchdeck receives a push from your connected Git provider, it creates a new deployment using the pushed changes.

Your configured build automation runs as normal before the build is transferred to your server.

If you're deploying over SSH, any configured SSH commands also run at their selected stages of the deployment.

If you push changes while another build is running, the new build will be queued automatically. If you push multiple times while a build is running, only your latest push will be queued to avoid unnecessary deployments.

Automatic deployments are currently available on paid plans.

Enabling automatic deployments doesn't prevent you from deploying manually. You can still start a deployment from Launchdeck whenever you need to. However, manual deployments can't be started while another build is running.

Related guides

Use build automation to prepare your application before it is transferred to your server.

When deploying over SSH, use SSH commands to run commands on your destination server as part of the deployment.

Learn more about how SSH releases are published in zero-downtime deployments.

Happy deploying!