This page describes steps to setup Continuous Deployment from Travis CI to Scalingo. Follow this guide to automatically deploy to Scalingo after a successful build.
Deploying to Scalingo is supported by the official dpl tool. You can use it as a stand alone tool and combine it with your workflow.
The dpl tool is used by Travis itself for deployment after builds. To
trigger a deployment after a success build on Travis you have to add the
deploy section to your
deploy: provider: scalingo api_key: <your Scalingo api token>
The recommended way to add your
api_key is to encrypt it through the
# Install the travis command if you don't have it yet gem install travis # Run the encrypt command in your project root travis encrypt <your Scalingo api token> --add deploy.api_key
If you don’t want to use the
api_key, you can specify
Scalingo API Token
Your API token is available on the ‘Profile’ page of Scalingo Dashboard.
api_key you can customize these optional parameters:
- app: App is the name of your app on Scalingo, it is extracted from the remote option.
on: Specify the branch to deploy from, default is
master. Change this if your code is not on master. You can also trigger the deploy from any branch:
deploy: on: all_branches: true
remote: Default remote is
scalingo. Change this if you have a different Git remote name.
username and password: replace the