On Fri, Sep 21, 2007 at 04:10:37PM +0200, Brandon Kelly wrote: > 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).
yes, deleting the index while the server is running isn't a good idea. You may also run Model.rebuild_index from a script after deployment to rebuild the index, or even create a rebuild_index deployment recipe via Capistrano. cheers, Jens -- Jens Krämer http://www.jkraemer.net/ - Blog http://www.omdb.org/ - The new free film database _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
