github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-24 01:38:56 -04:00
Code Issues Projects Releases Packages Wiki Activity

Backport PR #8483

Browse source 
---------

**Commit 1:**
Doc error: bin/kibana plugin doesn't restart Kibana!

* Original sha: 7c0ff89179
* Authored by Sina Sheikholeslami <ssheikholeslami@gmail.com> on 2016-09-27T15:02:13Z
* Committed by GitHub <noreply@github.com> on 2016-09-27T15:02:13Z

**Commit 2:**
Applied requested changes.

Since the process of restarting Kibana varies from OS to OS, I've included the means to restart it on Ubuntu machines as an example.

* Original sha: 488d0cb20e
* Authored by Sina Sheikholeslami <ssheikholeslami@gmail.com> on 2016-09-30T12:35:23Z
* Committed by GitHub <noreply@github.com> on 2016-09-30T12:35:23Z
This commit is contained in:
Elastic Jasper 2016-10-06 14:59:25 -04:00
parent 6073d9dd77
commit 8dd7eac1ec
1 changed files with 1 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/plugins.asciidoc
View file

@ -108,8 +108,7 @@ bin/kibana plugin --install username/sample-plugin --timeout 1m
==== Plugins and Custom Kibana Configurations
Use the `-c` or `--config` options to specify the path to the configuration file used to start Kibana. By default, Kibana
uses the configuration file `config/kibana.yml`. When you change your installed plugins, the `bin/kibana plugin` command
restarts the Kibana server. When you are using a customized configuration file, you must specify the
uses the configuration file `config/kibana.yml`. After you have changed the configuration file, you have to restart the Kibana server for changes to take effect (e.g. if Kibana is installed on an Ubuntu machine, you can restart it using `service kibana stop` followed by `service kibana start`). When you are using a customized configuration file, you must specify the
path to that configuration file each time you use the `bin/kibana plugin` command.
[float]