Ah figured it out! I think ts:stop requires that a configuration file exists... so after a deploy, since the config/ directory has been replaced and the sphinx config no longer exists, rake ts:stop fails...
My cap deploy:sphinx:restart is now "rake ts:config && rake ts:restart && rake ts:index" and it works. If anyone thinks there's an even better way, please let me know! On Apr 29, 5:01 pm, agib <[email protected]> wrote: > This is what my cap deploy:sphinx:restart task runs: > > "cd #{current_path} && rake thinking_sphinx:stop RAILS_ENV=# > {rails_env} && rake thinking_sphinx:configure RAILS_ENV=#{rails_env} > && rake thinking_sphinx:index RAILS_ENV=#{rails_env} && rake > thinking_sphinx:start RAILS_ENV=#{rails_env}" > > I'm running the latest sphinx-0.9.9 branch of TS and I'm getting > "searchd is already running" when I run cap deploy:sphinx:restart. If > I take out the rake ts:index it runs just fine... it seems like rake > ts:index is booting up searchd? Is that possible? > > Thanks! > > -ajg- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
