Subcommands introduced in 0.12.0
GIT-based deployment has been the traditional method of deploying applications in Dokku. As of v0.12.0, Dokku introduces a few ways to customize the experience of deploying via
git push. A GIT-based deployment currently supports building applications via both Buildpack and Dockerfile.
Initializing an Application
When an application is created via
git push, Dokku will create the proper
pre-receive hook in order to execute the build pipeline. In certain cases - such as when fronting deploys with the
git-http-backend - this may not be correctly created. As an alternative, the
git:initialize command can be used to trigger this creation:
In order for the above command to succeed, the application must already exist.
If the pre-receive hook was customized in any way, this will overwrite that hook with the current defaults for Dokku.
Changing the Deploy Branch
By default, Dokku will deploy code pushed to the
master branch. In order to quickly deploy a different local branch, the following GIT command can be used:
0.12.0, the correct way to change the deploy branch is to use the
git:set Dokku command.
Pushing multiple branches can also be supported by creating a receive-branch plugin trigger in a custom plugin.
Configuring the GIT_REV Environment Variable
Introduced in 0.12.0
Application deployments will include a special
GIT_REV environment variable containing the current deployment sha being deployed. For rebuilds, this sha will remain the same.
To configure the name of the
GIT_REV environment variable, run the
git:set command as follows:
This behavior can be disabled entirely on a per-app basis by setting the
rev-env-var value to an empty string: