Hi Blake,

Would another option be to copy the generated sphinx configuration
files across to the server and then use them when running the indexer
(using the native Sphinx commands rather than the Rake commands)? I
will definitely run the indexer on the same machine as the database
and search daemon!

Installing an entire Rails stack and my application logic on the
Sphinx server just to run the indexer seems very heavyweight to me. I
wonder if this (common) use case could be better supported by
thinking_sphinx in the future?

Cheers,
Graham

On Dec 9, 4:41 pm, "Blake Watters" <[EMAIL PROTECTED]> wrote:
> To keep your deployments simple, I would recommend getting a Rails stack on
> the machine responsible for handling the indexing. This will let you use the
> stock rake commands to regenerate the configuration and reindex painlessly.
> Otherwise, you are going to have to generate it somewhere else and get it
> deployed onto the search server before you can actually perform any
> indexing. I'd recommend doing your indexing on the same machine as the
> search indexer -- I've never tried running them segregated, but that's
> potentially a lot of data flying around.
>
> On Tue, Dec 9, 2008 at 7:21 PM, Graham Glass <[EMAIL PROTECTED]> wrote:
>
> > Hi everyone,
>
> > I have two servers; one is a dedicated database server running MySQL,
> > and the other is running a pack of mongrels with my Rails application
> > logic. I have Sphinx running in my development environment where the
> > database and application logic are on the same machine, and now I want
> > to deploy into production where they are on different machines.
>
> > It seems like I should store the Sphinx index and run the Sphinx
> > daemon on the database server, since they're both essentially storing
> > data and handling queries. So presumably I would run the Sphinx search
> > daemon there and access it from my mongrels when the user does a
> > search.
>
> > My question is: how do I get the initial index built without having to
> > also install Rails and my logic onto the database server? Ideally, I'd
> > like to keep the database server lean and mean and not install any
> > Rails code there. It's not clear to me where the indexer has to run in
> > relation to the Sphinx server and the relationship between where the
> > indexer runs and the Rails application.
>
> > Thanks!
> > Graham
--~--~---------~--~----~------------~-------~--~----~
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