Possible workaround for search issues

[amye]

readthedocs/readthedocs.org#1088

I'm not sure if we're using the same json that this issue references, but we could work on overriding the searchbox.html to replace this with something else.

Assigning to @humblec so that he can tell me if I am crazy or if this could work.

[amye]

@humblec, am I crazy? Could we overwrite this?

[humblec]

@amye finding out :) . Give me some time. I will get back.

[humblec]

@amye at present we use the standard templates of mkdocs and RTD (https://github.com/gluster/glusterdocs/blob/master/mkdocs.yml) without any customization . Looking at the thread, it seems to me that customizing the search could help us. @prashanthpai what do u think ?

[amye]

Either a custom Google search or a more elaborate elasticsearch setup is where I am thinking, but that will require @mscherer's help.

[amye]

Alternatively, @prashanthpai - this seems to be a confirmed workaround.
nodemcu/nodemcu-firmware@7dd89dd

[helmo]

I'm seeing 404's when I click in the search results on http://gluster.readthedocs.io

Would that also be solved by this? e.g. searching for 'brick' gives gluster - Brick Failure Detection as first result which returns a 404.

[nigelbabu]

Ugh, that file hasn't existed on the repo since 2015 :(

[prashanthpai]

This has been fixed to some extent by PR #255

[sankarshanmukhopadhyay]

If #255 address some pertinent parts of this - can we either split this issue out and/or close the part which is done? Or, close this entire issue itself?

[nigelbabu]

Yeah, this is safe to close.