On 10/04/2008, at 7:48 PM, Adhiraj Rankhambe wrote: >> 2. It's Java - which is extra overhead for some people - I certainly >> don't use any other Java tools, and I've not dealt with Java since >> Uni. Again, each to their own, but that may push non-Java people away >> from Solr. > > You don't need to know Java to use the acts_as_solr plugin. > > You just install the plugin and build the index for the first time. > Thenonwards, you just have to start the solr server by issuing a > command: > rake solr:start. > > Now tell me where's Java? > > That's pretty much it.
Sorry - first off, I have complete ignorance about acts_as_solr and Solr. My Java comment was in reference to the latter though, since you mentioned you can run it on 'a separate Java server', I assumed that's all it runs in. >>> 2. You have to write a lot of sql code in the configuration file for >>> indexing and searching data. >> >> This very much depends on the plugin you use. I'm reasonably sure >> this >> isn't required for Ultrasphinx, and it's definitely not for Thinking >> Sphinx (my own plugin, as mentioned earlier in this thread - yes, >> I've >> got some level of bias). > > Ultrasphinx works only on Rails 2.0. Granted, this is a problem if you're shoehorning Sphinx into an existing app - but I'm guessing most people starting new projects would be using 2.0 (or even edge in preparation for 2.1?) Cheers -- Pat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
