Oh, and we are also using datetime_delta.

On Apr 22, 2:07 pm, Yaroslav Markin <[email protected]> wrote:
> Hi.
>
> Since which t_s version is this supported? We are using 1.3.11 for
> Rails 2.3.x application, our production deployment is 1 sphinx server
> plus N application servers, and I get the warning each time I run a
> rake task or script/delayed_job, for example.
>
> Setting version: 0.9.9 (and it is 0.9.9 indeex) in sphinx.yml on all
> servers does not help at all.
>
> My config is like this:
>
> production:
>   address: 192.168.0.3
>   version: 0.9.9
>   charset_type: utf-8
>   morphology: stem_enru
>   html_strip: 1
>   seamless_rotate: 1
>
> On Apr 11, 9:38 am, Pat Allan <[email protected]> wrote:
>
>
>
>
>
>
>
> > Hi Kenn
>
> > You'll just need to tell Thinking Sphinx which version of Sphinx it's 
> > dealing with in your config/sphinx.yml file:
>
> >   production:
> >     version: 0.9.9
>
> > (Or 0.9.8 or 1.10-beta).
>
> > Cheers
>
> > --
> > Pat
>
> > On 08/04/2011, at 9:00 AM, kenn wrote:
>
> > > In our production environment, Sphinx is installed only on a dedicated
> > > host and not on others.
>
> > > I see the "Sphinx cannot be found on your system" warning whenever I
> > > run rake tasks with the rails environment, or "rails console", or cap
> > > deploy:migrations.
>
> > > Is there any way I can suppress that message?
>
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Thinking Sphinx" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to 
> > > [email protected].
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/thinking-sphinx?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Thinking Sphinx" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/thinking-sphinx?hl=en.

Reply via email to