Plugins: Allow plugins to serve a _site, automatically download github plugins

[kimchy]

Plugins can now have sites in them, any plugin that exists under the plugins directory with an _site directory, its content will be statically served when hitting /_plugin/[plugin_name]/.

Installed plugins that do not contain any java related content, will automatically be detected as site plugins, and their content will be moved under _site.

Plugins will automatically be downloaded from github if they follow the user_name/repo_name structure.

For example, in order to use the mobz/elasticsearch-head plugin, we can execute: bin/plugin -install mobz/elasticsearch-head. Then, we can point our browser to http://localhost:9200/_plugin/head/ and see the site.

[clintongormley]

Very nice!

[mahendra]

Coolness!! :-)

[medcl]

coolala

[mobz]

I will definitely be promoting this as the way to use es-head once 0.17 is out. As well as overall awesomeness, there are really useful features of html5 that you can only use when serving the site from http: rather than file:

[mahendra]

I feel this blurs the difference between CouchDB and Elasticsearch. CouchDB is a big proponent of hosted HTML/JS apps. With this (maybe) one can host search driven apps right inside ES. :-)

[janl]

Cool Stuff :)

[karmi]

Awesome!!!

[lukas-vlcek]

Will it always refer to master in repo? Or is there any way to refer to particular tags or even commits?
(I was looking into code, it seems there is a way how to specify at least version but it is not yet documented.)

[kimchy]

It will try and download first based on the elasticsearch version, first, download a file (from github download, names with ES version), then a tag, and last, master. So, you can simply tag your project and match the elasticsearch version that comes out.