Is the text search on Mongo DB better? For a short while I had the idea to implement database interface using ElasticSearch instead of Mongo/REDIS but the DB design is very much tailored to REDIS and I expect higher effort than using the plugin way..

Background: The story started as I was unhappy with search results and answer was it is limitation in using a simple search library for REDIS (maybe there are others doing better ...). So I could imagine that it behaves better on Mongo. Personally I have no experience with Mongo so I did not consider to use it ...

In the meanwhile I added the search URL as hook - and I made a pull request to allow me to replace original search function by an admin setting to disable DB search (then original search url is not registered). If somebody wants to play around with it can take my forked NodeBB repository tepmorary. At least this allow me to continue on search functions independently until the NodeBB team told me whats the best way to register new search url ...

To mak it short:
npm install seti123/NodeBB
Rest of procedure as usual ...
then npm install seti123/nodebb-plugin-elasticsearch

Details described in my github repository or page mentioned above.

right, you need to force users to search for topic first - startpage like google
Maybe my search plugin will end at the cover page

Anybody thought about a WebRTC integration. To start calling and chatting with other users.
To give you an impression look at https://twelephone.com/

As mentioned in the other post, I just started on the plugin might need some support. And yes, I'm using elasticsearch.js maintained by ElasticSearch as library to perfom indexing and search.

There is a search function in NodeBB. But I used it and could not find my topics. So I asked for improvement and somebody else asked about a lot of specific search features (e.g. order by most replys etc.). As I'm used to ElasticSearch I catched up the idea to make a plugin. But I'm not very familar with the plug-in API. Some Hooks I wanted (e.g. overwrite the inbuid search function) might not be available. Another issue might be to update edited posts (I get no event for it ..).

On my prototype I get very good search results (as expected) and can use complete Lucene query syntax.

I think with little work of the NodeBB team and somebody helping me to point to the right (new) hooks in my plugin would create high value for scalable large NodeBB sites.

I plan to use it in my intranet and closed customer support platform (that's why I asking for a lot of security features, removal of social network buttons etc.)

I'm looking for helpers with NodeBB plugin experience. I created NodeBB plugin for elasticsearch. It is already indexing the posts but I would like for example overload the route app.('/search:term' ..) with my search functions.
As proof of concepts I modified api.js of NodeBB source on my local machine (check here
And asked on github to get more hooks to be able to update the search index and provide autocopletion etc. ....
https://github.com/designcreateplay/NodeBB/issues/786?source=cc

Anybody interested to help you can join me on GitHub
http://seti123.github.io/nodebb-plugin-elasticsearch

BR
Stefan

is it possible to redirect user to "Login Page" or Cover Page which leads then to "Login" instead of showing categories.
Maybe this are only visible for registered users ...