Files
dokku/docs/advanced-usage/plugin-management.md
Jose Diaz-Gonzalez ea0089b207 Release 0.12.0
# History

## 0.12.0

### Bug Fixes

- #3146: @josegonzalez Fix non ubuntu installs
- #3138: @josegonzalez Use correct path for /etc/default file
- #3137: @josegonzalez Ensure we can disable setting the rev-env-var
- #3131: @axilleas Capitalize log sentence when renaming containers
- #3128: @Modicrumb Improve windows vagrant experience
- #3105: @znz Follow renaming from deploy-method to deploy-source
- #3101: @josegonzalez Handle stopped nginx during debian installation

### New Features

- #3141: @josegonzalez Centralize app existence checks into the apps plugin
- #3147: @josegonzalez Create proxy:ports-set call
- #3145: @josegonzalez Add report trigger
- #3144: @josegonzalez Increase curl max timeout to 600 seconds (10 minutes)
- #3107: @znz Remove unused password in ssl cert generation
- #3095: @josegonzalez Migrate env for NGINX_* to PROXY_*
- #3140: @josegonzalez Add newline to config:get output
- #3139: @josegonzalez Add ability to initialize a git repository out of band
- #3111: @josegonzalez Upgrade herokuish to 0.4.0
- #3110: @josegonzalez Upgrade herokuish to 0.3.36
- #3106: @znz Remove unnecessary shellcheck disable
- #3098: @josegonzalez Pull herokuish from docker hub when installing via package
- #3100: @josegonzalez Properly handle invalid process type entries during DOKKU_SCALE generation
- #3097: @josegonzalez Update herokuish to 0.3.35

### Documentation

- #3148: @josegonzalez Use consistent terms for domains, apps, and commands
- #3135: @josegonzalez Revert "Clarify that the checks plugin only matches content start"
- #3134: @tomdyson Fix typo in upgrading docs
- #3119: @TomasHubelbauer Link through to the application deployment page after the installation
- #3118: @Tyilo Clarify that the checks plugin only matches content start
- #3113: @ilyapoz Fix proxy management link
- #3112: @josegonzalez Minor doc css fixes
- #3104: @sarendsen Add dokku-limit to plugins documentation
- #3108: @znz Update plugin list output
2018-04-07 17:16:14 -04:00

4.3 KiB

Plugin Management

New as of 0.4.0

plugin:disable <name>                    # Disable an installed plugin (third-party only)
plugin:enable <name>                     # Enable a previously disabled plugin
plugin:install [--core|git-url [--committish tag|branch|commit|--name custom-plugin-name]]           # Optionally download git-url (with custom tag/committish) & run install trigger for active plugins (or only core ones)
plugin:install-dependencies [--core]     # Run install-dependencies trigger for active plugins (or only core ones)
plugin:list                              # Print active plugins
plugin:uninstall <name>                  # Uninstall a plugin (third-party only)
plugin:update [name [committish]]        # Optionally update named plugin from git (with custom tag/committish) & run update trigger for active plugins
# for 0.3.x
cd /var/lib/dokku/plugins
git clone <git url>
dokku plugins-install

These commands require root permissions as the install and install-dependencies plugin triggers may utilize commands such as apt-get. For non-core plugins, please inspect those plugins before running the following command as root user.

Usage

You can list all installed plugins using the plugin command:

dokku plugin
plugn: dev
  00_dokku-standard    0.12.0 enabled    dokku core standard plugin
  20_events            0.12.0 enabled    dokku core events logging plugin
  apps                 0.12.0 enabled    dokku core apps plugin
  build-env            0.12.0 enabled    dokku core build-env plugin
  certs                0.12.0 enabled    dokku core certificate management plugin
  checks               0.12.0 enabled    dokku core checks plugin
  common               0.12.0 enabled    dokku core common plugin
  config               0.12.0 enabled    dokku core config plugin
  docker-options       0.12.0 enabled    dokku core docker-options plugin
  domains              0.12.0 enabled    dokku core domains plugin
  enter                0.12.0 enabled    dokku core enter plugin
  git                  0.12.0 enabled    dokku core git plugin
  logs                 0.12.0 enabled    dokku core logs plugin
  named-containers     0.12.0 enabled    dokku core named containers plugin
  network              0.12.0 enabled    dokku core network plugin
  nginx-vhosts         0.12.0 enabled    dokku core nginx-vhosts plugin
  plugin               0.12.0 enabled    dokku core plugin plugin
  proxy                0.12.0 enabled    dokku core proxy plugin
  ps                   0.12.0 enabled    dokku core ps plugin
  repo                 0.12.0 enabled    dokku core repo plugin
  shell                0.12.0 enabled    dokku core shell plugin
  ssh-keys             0.12.0 enabled    dokku core ssh-keys plugin
  storage              0.12.0 enabled    dokku core storage plugin
  tags                 0.12.0 enabled    dokku core tags plugin
  tar                  0.12.0 enabled    dokku core tar plugin

Installing a plugin is easy as well using the plugin:install command. This command will also trigger the install pluginhook on all existing plugins.

dokku plugin:install https://github.com/dokku/dokku-postgres.git
-----> Cloning plugin repo https://github.com/dokku/dokku-postgres.git to /var/lib/dokku/plugins/available/postgres
Cloning into 'postgres'...
remote: Counting objects: 646, done.
remote: Total 646 (delta 0), reused 0 (delta 0), pack-reused 646
Receiving objects: 100% (646/646), 134.24 KiB | 0 bytes/s, done.
Resolving deltas: 100% (406/406), done.
Checking connectivity... done.
-----> Plugin postgres enabled

You can also uninstall a third-party plugin using the plugin:uninstall command:

dokku plugin:uninstall postgres
-----> Plugin postgres uninstalled

Enabling or disabling a plugin can also be useful in cases where you are debugging whether a third-party plugin is causing issues in your Dokku installation:

dokku plugin:disable postgres
-----> Plugin postgres disabled
dokku plugin:enable postgres
-----> Plugin postgres enabled

Finally, you can update an installed third-party plugin. This should be done after any upgrades of Dokku as there may be changes in the internal api that require an update of how the plugin interfaces with Dokku.

dokku plugin:update postgres
Plugin (postgres) updated