-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin install command #4204
Comments
Closed by #4406 |
PR #4942 is up to provide doc coverage. |
I need install pluggin from local directory. Any idea??? |
From the documentation ( "You can also install a plugin manually by moving the plugin file to the Please use our discussion forums (https://discuss.elastic.co/) for support On Thu, Mar 17, 2016 at 1:11 PM, daguero notifications@github.com wrote:
|
Kibana plugins will allow you to add features and new applications to kibana. This should work identically to the elasticsearch plugin system, with the exception that
bin/kibana
will serve as the command, instead ofbin/plugin
. Pretty much its sole purpose is to copy things into theplugins
directory.Most of the following is copied nearly wholesale from:
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-plugins.html
Installing plugins can either be done manually by placing them under the plugins directory, or using the plugin script. Several plugins can be found under the elasticsearch organization in GitHub, starting with elasticsearch-.
Download.elastic.co
Installing plugins typically take the following form:
or for example
The plugins will be automatically downloaded in this case from download.elastic.co
Github
We should also support installing plugins from github. In this case the user will always get the latest version
Removal
Should fully remove the plugin, config and all. You remove it, its gone
Verbosity
The default mode should provide the user with feedback on the status of the plugin install. The user should be able to pass
--silent
to keep that quiet.Timeouts
Exit codes
The text was updated successfully, but these errors were encountered: