On Fri, Sep 21, 2007 at 02:31:04AM +0200, Brandon Kelly wrote: > Thanks for the quick response Jens. > > Okay -- my problem apparently is that I've been deploying new code > (which stops and starts the ferret server), then I would go in and > delete the index. So the index gets recreated, but the DRB server > "remembers" the previous index, or settings, or whatever. > > When I follow these steps, the index is created correctly, and the > analyzer works fine... > > 1. deploy new code > 2. script/ferret_stop > 3. rm -rf index/production > 4. script/ferret_start > > The key for me to remember is to stop the DRB server BEFORE deleting the > index. > > I've created a simple capistrano recipe to handle this in the future.
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. Cheers, Jens -- Jens Krämer webit! Gesellschaft für neue Medien mbH Schnorrstraße 76 | 01069 Dresden Telefon +49 351 46766-0 | Telefax +49 351 46766-66 [EMAIL PROTECTED] | www.webit.de Amtsgericht Dresden | HRB 15422 GF Sven Haubold, Hagen Malessa _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
