Hum, tks. Anyway, it's not desirable for us (for now) to have that implemented in the backoffice. Is there a way of force reindex, for isntance, in a rails cron?
Regards, Miguel Jens Kraemer wrote: > On Tue, Jul 03, 2007 at 09:25:53PM +0200, Miguel Carvalho wrote: >> backoffice) are not searchable. >> >> Does acts_as_ferret indexes on change ops, like insert,delete, update? >> Is that the reason why i can't see the new ones? > > Exactly. You should use aaf in your backoffice application, too. Keep in > mind to use the same acts_as_ferret settings (fields, analyzer and such) > as you do in your frontend app. And use the DRb server to avoid > collisions when both applications want to access the index. > > In the end it doesn't matter where you run your DRb server (frontend or > backoffice), but to me it seems good to keep the index in the backoffice > app since that's where the data is created/changed. > > 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 -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
