I do have the site setup this way. My deploy script stops and starts the DRB server without touching the index (which is what I want most of the time).
My problem arose when I needed to delete the index. I'd deploy new code, DRB would restart with the old index in place... then I'd delete the old index (while DRB server was running)... and watch it rebuild. The rebuilt index had problems. Wasn't until I realized I need to delete the index only when DRB server isnt' running. (at least that works for me). Thanks again. > cool. I usually put the index directory into shared/ and symlink it into > the current release during deploment. This saves you the index rebuild > after deploying. -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
