It takes care of querying, managing search state and updating your UI. There are 10 built-in components: https://docs.appbase.io/docs/reactivesearch/vue/overview/Sho... which can help one get started in minutes. However, it's very much designed to allow bringing in your own UI components and design systems.
I will have to relook at this - the comment is from a year ago when they weren't using React.
On a cursory look, it still seems to use a Node.JS based server [1]. One of the key side effects of needing a server is that there is a more involved distribution + installation process. You just can't run it on a static server like github pages or as a browser extension.
Not that I know of, but given the similarities in the underlying APIs - we would be open to supporting this and help guide the implementation if someone is interested in sending a PR. Feel free to file an issue - https://github.com/appbaseio/dejavu/issues/.
Yes, we don't focus on admin related features atm. Elasticsearch head or Elasticsearch HQ [1] are good options for doing this.
Fun fact: We actually started out with elasticsearch-head, but realized it was really hard to hack on (this was ~2y ago) and decided to create Dejavu. Imo, the key difference is we have focused a lot on how to get the data indexed (mappings, bring your CSV/JSON files) and have the raw data visualized (via UI based filters or DSL queries).
It's complementary to Kibana, I would say. Dejavu gives the raw data view as well as an ability to add/update data along with mappings. It also comes with an importer view where you can add JSON / CSV files to directly import into ES. Doing this otherwise currently is a major PITA.
Kibana is more for dashboarding and visualization, Dejavu gives you control of the raw data views and indexing operations.
Hi HN! I am Sid, one of the authors of ReactiveSearch.
We have built ReactiveSearch with the goal of providing cross-platform UI components for building a great search experience. And today, I am excited to share both the React (for Web) and React Native (for iOS, Android) flavors of the library.
The library is architected around the concept of reactivity. A UI component in ReactiveSearch can subscribe to and compose its state from any other component. This creates a reactive feedback loop of changes when a user interacts with any one component. You can choose from the current 30+ pre-built components or bring your own design components to work with ReactiveSearch. Would love to hear your thoughts!
We're just putting out the 1.0 release of ReactiveSearch Vue - https://medium.appbase.io/reactivesearch-vue-1-0-ui-componen.... It's a sister library to ReactiveSearch for React, with a similar aim of removing the pain out of building search UIs.
It takes care of querying, managing search state and updating your UI. There are 10 built-in components: https://docs.appbase.io/docs/reactivesearch/vue/overview/Sho... which can help one get started in minutes. However, it's very much designed to allow bringing in your own UI components and design systems.
Direct Github link: https://github.com/appbaseio/reactivesearch.