Warning: As of 0.24.0, this functionality is deprecated in favor of the
git:from-archivecommand. It will be removed in a future release, and is considered unmaintained. Users are highly encouraged to switch their workflows to
New as of 0.4.0
tar:from <app> <url> # Loads an app tarball from url tar:in <app> # Reads an tarball containing the app from stdin
dokku ps:rebuild APPon an application deployed via the
tarplugin, the following may occur:
- Applications previously deployed via another method (
git): The application may revert to a state before the latest custom image tag was deployed.
- Applications that were only ever deployed via the
tarplugin: The application will be properly rebuilt.
Please use the appropriate
tarcommand when redeploying an application deployed via tarball.
In some cases, it may be useful to deploy an application from a tarball. For instance, if you implemented a non-Git based deployment plugin, tarring the generated artifact may be an easier route to interface with the existing Dokku infrastructure.
You can place the tarball on an external webserver and deploy via the
dokku tar:from node-js-app https://dokku.me/releases/node-js-app/v1
As an alternative, a deploy can be trigged from a tarball read from stdin using the
# run from the generated artifact directory tar c . $* | dokku tar:in node-js-app