ssetem - Hackdot

Re:Searchkit 0.8 – React UI Components for Elasticsearch on Monday March 21, 2016 @05:33AM (#11326974)

Thanks, solr support is a possiblity, we will probably take a look in the future

Re:Searchkit 0.8 – React UI Components for Elasticsearch on Sunday March 20, 2016 @04:21PM (#11324472)

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.

Re:Show HN: Searchkit – React components for elasticsearch on Monday January 04, 2016 @12:56PM (#10837122)

Hi I am the Co-Author of Searchkit

We have now switched to Apache license Due to interest and our wish is for many new contributors to add to Searchkit's ecosystem + component library https://github.com/searchkit/searchkit/blob/master/LICENSE We will be working hard in the next weeks to add to the developer documentation, and walkthroughs on making custom components. Thanks!

Re:Show HN: Searchkit – React components for elasticsearch on Monday January 04, 2016 @12:53PM (#10837097)

We have switched to Apache license Due to interest and our wish for many new contributors to add to Searchkit's ecosystem + component library

https://github.com/searchkit/searchkit/blob/master/LICENSE

We will be working hard in the next weeks to add to the developer documentation, and walkthroughs on making custom components.

Thanks!

Re:Show HN: Searchkit – React components for elasticsearch on Monday January 04, 2016 @11:26AM (#10836431)

fixed now :), try the demo now http://searchkit.co

Re:Show HN: Searchkit – React components for elasticsearch on Monday January 04, 2016 @11:25AM (#10836427)

thanks for the feedback, this is fixed now :)

Re:Show HN: Searchkit – React components for elasticsearch on Monday January 04, 2016 @06:19AM (#10834925)

thanks, will fix this today :D

Re:Show HN: Searchkit – React components for elasticsearch on Monday January 04, 2016 @06:06AM (#10834891)

Thanks, we can look into higher order components for wrapping and overriding blank states etc.

The service layer is purely opt in, and its a thin proxy incase you want to apply permissions, it speaks elasticsearch purely, this is one thing we don't want to change. E.g. our demos actually connect direct to a read only elasticsearch instance