Deploying Repositories

If your deploy source is a repository Sliplane automatically deploys a new version of your application everytime that you push a new commit to the previously selected branch in your repository. We also redeploy your application if you update any of the settings, such as the environment variables or the build command. If your new deploy fails, the previous version of your application will remain online. Ship fast, ship often!

You can disable automatic deploys in your service settings and deploy your service by sending a GET request to the deploy hook that you can find in your service settings. Keep this URL secret, as anyone with it can deploy your service.

Deploying Services from Dockerhub

Follow the "deploy service" workflow to deploy public Docker images. If you want to upgrade your image, head over to service settings and change the image tag to the wanted version. A new deploy will be started when you save your updated settings. To update your service with the tag "latest" you can invoke the "Redeploy" action on your service card. This will automatically pull the latest version. Another option is to send a GET request to the deploy hook in your service settings.

What happens if a new deploy fails?

If you push code and the build or start command fails, we will not redirect the traffic to the new version of your application. Instead, we will keep the previous version of your application online. This way, your users will not experience any downtime. You will also be able to see the logs of the failed deploy in the logs section of your service!

If you have any questions or need assistance with your deploys, please do not hesitate to contact us. We're always here to help!

Getting started