You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
README examples and even code comments use usr/local/awesome/elasticsearch-version/plugins as a plugin_dir value. I'm not sure if that's a real world example or not. Surely ElasticSearch provides a standard plugins directory: why doesn't this cookbook have a default for that? Why do the users have to even think about where to put the plugins?
The text was updated successfully, but these errors were encountered:
Have you tried to use the elasticsearch_plugin with the defaults? It actually does default to the typical path. This cookbook was written to handle a very commonly requested case of multiple instances per server. We'll try to provide better documentation in the future.
- Test default simple plugin install as part of default test suite.
- Add example using the test to the documentation. Add more simple examples to the README.md, demonstrating the defaults. RE: #345
- Test default simple plugin install as part of default test suite.
- Add example using the test to the documentation. Add more simple examples to the README.md, demonstrating the defaults. RE: #345
README examples and even code comments use
usr/local/awesome/elasticsearch-version/plugins
as aplugin_dir
value. I'm not sure if that's a real world example or not. Surely ElasticSearch provides a standard plugins directory: why doesn't this cookbook have a default for that? Why do the users have to even think about where to put the plugins?The text was updated successfully, but these errors were encountered: