You could proxy using nginx to allow read only access to specific endpoints, there's a few good posts about it going into better detail than me, for example:
This looks great! But could it be modified to work off of an Apache Solr backend instead? If not, do you know a similarly nice group of front-end components for Solr?
Comments
Noob Question; how do we ensure that full query interface of elasticsearh isn't exposed to the browsers?
PS: I m using elasticsearch in the backend.
You could proxy using nginx to allow read only access to specific endpoints, there's a few good posts about it going into better detail than me, for example:
http://blog.eagerelk.com/securing-elasticsearch-using-nginx-...
We proxy the elasticsearch connection through the server and sanitize the request. Some installations also add more filters like permissions filter.
In future releases, we're going to improve on this. Stay tuned!
http://docs.searchkit.co/stable/docs/server/searchkit_expres...
we ship a node.js proxy to hide your elastic instance, and you can add permission filters etc.
This looks great! But could it be modified to work off of an Apache Solr backend instead? If not, do you know a similarly nice group of front-end components for Solr?
Thanks, solr support is a possiblity, we will probably take a look in the future
Very similar instantsearch.js (which is also react components) for Algolia search.
Having this for elasticsearch is very useful indeed, get products out there with a consistent search UI.
Yes, instantsearch.js is built on top of React. But it's not a React component yet.
See https://github.com/algolia/instantsearch.js/issues/920
Indeed we are working to provide it as React components also. Thanks for the mention :)