Hi all,
I want to build UI for Solr that get result to the user and also update the
solr back (set for specific field)
I start using ajax-solr because there is good tutorial and it's easy to use,
but I didn't saw an example for update, and also I'm not sure the code is
stable (no release in
You should not be exposing Solr directly to the user, that's like
giving them a database admin account. Unless you REALLY know what you
are doing. So, the Javascript UIs are mostly for internal purposes and
for people to play with Solr.
Therefore, usually, there is a server-side component that
Actually I disagree Alex. We build JS apps that talk straight to Solr all
the time.
However, we are sure to lock it down pretty heavily. Moreover, these cases
almost never have sensitive information. You need to think through the
worst case. As search is often a secondary artifact of a primary
I am happy to be corrected, but that repository says "This repository
gives a basic outline to creating a functional reverse proxy with
Nginx" as well as the famous last words ("e.t.c.") . Which is why I
feel it is not exactly a turnkey solution I can recommend to a new
Solr user. Is there an
Nope, it's more of a template. But I still think its simpler than coding up
and deploying an API that acts as a relay to a search endpoint. Again, I
don't think this is right for every use case. But we use it for
http://solr.quepid.com
In the nginx.conf, you need to basically update two spots
#
That sounded defensive :) Just sharing our experience. I also don't mind
being corrected, especially if there's an issue with the config here.
Cheers
-Doug
On Thu, Nov 26, 2015 at 11:28 AM, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> Nope, it's more of a template. But I still
If it works for Quepid, it is good enough for me :-) I might actually
try that for one of my upcoming projects where I do need a read-only
Solr.
But this is for read-only setup only. So, still not really useful for
the original request's second part: "There is another option?
Something that also
Oh right, yes I missed that. My fault. I definitely wouldn't open up the
update portion!
-Doug
On Thu, Nov 26, 2015 at 11:51 AM, Alexandre Rafalovitch
wrote:
> If it works for Quepid, it is good enough for me :-) I might actually
> try that for one of my upcoming projects