Ah, I'd forgotten index does its own conf file generating, it doesn't call the configure rake task... I wanted to make sure the error was in writing the file instead of reading it.
So, two things: what happens when you delete (or maybe just rename) the existing conf file? And what's the stack trace from the rake task? Seems it's missing from the output below. -- Pat On 12/05/2010, at 5:00 PM, Michael wrote: > >> What's the output when you run the rake task with --trace? > > C:\[path\to\project]>rake ts:index --trace > (in C:/[path/to/project]) > ** Invoke ts:index (first_time) > ** Invoke thinking_sphinx:index (first_time) > ** Invoke thinking_sphinx:app_env (first_time) > ** Execute thinking_sphinx:app_env > ** Invoke environment (first_time) > ** Execute environment > ** Execute thinking_sphinx:index > Generating Configuration to C:/[path/to/project]/config/ > development.sphinx.conf > FATAL: config file ''C:/[path/to/project]/config/ > development.sphinx.conf'' does not exist or is not readable > ** Execute ts:index > > -- > 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. > -- 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.
