Skip to content
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.

Sign up for GitHub

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

Clarify when overriding plugin_dir is necessary #349

Merged
merged 1 commit into from
Jul 17, 2015
Merged

Clarify when overriding plugin_dir is necessary #349

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -182,10 +182,16 @@ Actions: `:install`, `:remove`
Installs or removes a plugin to a given elasticsearch instance and plugin
directory.

When running a single instance per machine (VM, etc), it's typically
sufficient to rely on the default value of `plugin_dir`:

```
elasticsearch_plugin 'mobz/elasticsearch-head'
```

To run multiple instances per machine, an explicit `plugin_dir` location
has to be provided:

```
elasticsearch_plugin 'mobz/elasticsearch-head' do
plugin_dir '/usr/local/awesome/elasticsearch-1.5.0/plugins'
Expand Down