Anynines Deployment
This page documents deployments using the dpl v2. Please see our blog post for details. You can check previous dpl v1 documentation here.
You can deploy your application to anynines after a successful build on Travis CI.
For a minimal configuration, add the following to your .travis.yml
:
deploy:
provider: anynines
username: <username>
password: <encrypted password>
organization: <organization>
space: <space>
edge: true # opt in to dpl v2
Status #
Support for deployments to Anynines is in alpha. Please see Maturity Levels for details.
Known options #
Use the following options to further configure the deployment.
username |
anynines username — required, type: string |
password |
anynines password — required, secret, type: string |
organization |
anynines organization — required, type: string |
space |
anynines space — required, type: string |
app_name |
Application name — type: string |
buildpack |
Buildpack name or Git URL — type: string |
manifest |
Path to the manifest — type: string |
Shared options #
cleanup |
Clean up build artifacts from the Git working directory before the deployment — type: boolean |
run |
Commands to execute after the deployment finished successfully — type: string or array of strings |
Environment variables #
All options can be given as environment variables if prefixed with ANYNINES_
.
For example, password
can be given as ANYNINES_PASSWORD=<password>
.
Securing secrets #
Secret option values should be given as either encrypted strings in your build
configuration (.travis.yml
file) or environment variables in your repository
settings.
Environment variables can be set on the settings page of your repository, or
using travis env set
:
travis env set ANYNINES_PASSWORD <password>
In order to encrypt option values when adding them to your .travis.yml
file
use travis encrypt
:
travis encrypt <password>
Or use --add
to directly add it to your .travis.yml
file. Note that this command has to be run in your repository’s root directory:
travis encrypt --add deploy.password <password>
Pull Requests #
Note that pull request builds skip the deployment step altogether.