On Mon, 4 Mar 2019 at 19:21, Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On 3/3/19 11:28 PM, Clement Verna wrote: > > > The frontend will be an independent application that we will need to > > develop or as suggested by Ryan we may explore using src.fp.o. Having > > a separated backend for search capabilities makes a lot of sense to me > > since that makes this service easy to reuse by other apps and let > > people write their custom client if they wish to do so. > > So, really this is about replacing xiapan with ES, right? > Since we will still need a app to interface with those results.. Yes this is the first step for me, once we replace the backend we can get creative on how we want to replace the frontend :-) > > > With the idea to have a separate search backend with HTTP API, xapian > > is a problem since we have to write the HTTP wrapper around xapian's > > API to make it available to all, there is xapiand > > (https://kronuz.io/Xapiand/) but the project seems fairly recent and > > not yet mature. The other benefits of Elasticsearch are a maintained > > Python client, a maintained Javascript client, better documentation, > > largely adopted solution (easier to get people interested in). > > Yeah, all good points. > > kevin > > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
