|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|A web front end for an elastic search cluster|
|Prestissimo||6,331||76||45||2 years ago||36||February 16, 2020||38||mit||PHP|
|composer parallel install plugin|
|Docker Maven Plugin||2,576||85||2||2 years ago||305||January 15, 2020||20||apache-2.0||Java|
|INACTIVE: A maven plugin for Docker|
|🗣️ Simple self-hosted node app for Disqus-like drop-in commenting on static websites|
|:key: A login/register flow built with React&Redux|
|Gitlab Plugin||1,418||a day ago||237||gpl-2.0||Java|
|A Jenkins plugin for interfacing with GitLab|
|Sudo_pair||1,169||1||1||10 months ago||5||March 27, 2020||16||apache-2.0||Rust|
|Plugin for sudo that requires another human to approve and monitor privileged sudo sessions|
|Core.js||1,079||8||416||a day ago||60||July 10, 2023||14||mit||TypeScript|
|Extendable client for GitHub's REST & GraphQL APIs|
|Nativescript Plugin Firebase||1,018||125||12||6 months ago||159||November 05, 2020||594||mit||TypeScript|
|:fire: NativeScript plugin for Firebase|
|Dragonproxy||996||2 years ago||25||gpl-3.0||Java|
|🐲 A proxy to allow Minecraft: Bedrock clients to connect to Minecraft: Java Edition servers.|
There are multiple ways of running elasticsearch-head.
git clone git://github.com/mobz/elasticsearch-head.git
npm run start
This will start a local webserver running on port 9100 serving elasticsearch-head
docker run -p 9100:9100 mobz/elasticsearch-head:5
docker run -p 9100:9100 mobz/elasticsearch-head:2
docker run -p 9100:9100 mobz/elasticsearch-head:1
sudo elasticsearch/bin/plugin install mobz/elasticsearch-head
sudo elasticsearch/bin/plugin -install mobz/elasticsearch-head/1.x
sudo elasticsearch/bin/plugin -install mobz/elasticsearch-head/0.9
This will automatically download the appropriate version of elasticsearch-head from github and run it as a plugin within the elasticsearch cluster. In this mode elasticsearch-head automatically connects to the node that is running it
This is an experimental feature which creates a local proxy for many remote elasticsearch clusters
localhost9200.jsonas example )
npm run proxy
At the moment it only works with
grunt server running on http://localhost:9100
By default elasticsearch exposes a http rest API on port 9200 which elasticsearch-head connects to.
When not running as a Chrome extension or as a plugin of elasticsearch (which is not even possible from version 5), you must enable CORS in elasticsearch, or else your browser will reject elasticsearch-head’s requests due to violation of the same-origin policy.
In elasticsearch configuration;
http.cors.allow-originbecause no origin allowed by default.
http.cors.allow-origin: "*"is valid value, however it’s considered as a security risk as your cluster is open to cross origin from anywhere.
elasticsearch-head will add basic auth headers to each request if you pass in the correct url parameters
You will also need to add
http.cors.allow-headers: Authorization to the elasticsearch configuration
elasticsearch x-pack requires basic authentication and CORS as described above. Make sure you have the correct CORS setup and then open es-head with a url like “http://localhost:9100/?auth_user=elastic&auth_password=changeme”
Parameters may be appended to the url to set an initial state eg.
base_uriforce elasticsearch-head to connect to a particular node.
dashboardexperimental feature to open elasticsearch-head in a mode suitable for dashboard / radiator. Accepts one parameter
auth_useradds basic auth credentials to http requests ( requires elasticsearch-http-basic plugin or a reverse proxy )
auth_passwordbasic auth password as above (note: without additional security layers, passwords are sent over the network in the clear )
langforce elasticsearch-head to use specified ui language (eg: en, fr, pt, zh, zh-TW, tr, ja)
To contribute to elasticsearch-head you will need the following developer tools
npm install# downloads node dev dependencies
grunt dev# builds the distribution files, then watches the src directory for changes (if you have an warning like "Warning: Task “clean” failed. Use —force to continue.", well use —force ;) )
Changes to both _site and src directories must be committed, to allow people to
run elasticsearch-head without running dev tools and follow existing dev patterns,
such as indenting with tabs.
To contribute an internationalisation
src/app/langs/en_strings.jsprefixed with your language code