I''m finishing up a rails app that uses Ferret / AAF. I''m using shared hosting provided by railsplayground.com. My app is pretty small and is never going to get much traffic, so I''m going with the cheapest plan. Unfortunately, the cheapest plan doesn''t allow any static processes. I''ve read multiple recommendations to use a DRB server when using ferret in production, but I can''t on this plan since using a DRB server requires a static process. So far Ferret/AAF have worked great and I haven''t seen any errors, index corruption, or any other problems. Do I really need to use the DRB server for Ferret? Since I haven''t experienced any errors yet, I''m not sure what these will look like. I''ve got the exception notifier plugin installed, but will I get notified of ferret errors? My understanding of how this plugin works is that it handles errors in ApplicationController, so any error that does not occur as a result of a controller/action will not get handled. I''m just not sure what to be looking for to tell if I need to upgrade and use the DRB server or not. One other useful piece of information: my site has 1 (and only 1) admin user, and he is the only one that does any C, U or D (of "CRUD")--visitors to my website will only ever read the models, so there should never be a time where multiple people will be making simulaneous changes that need to be indexed. Thanks, Myron -- Posted via http://www.ruby-forum.com/.
> One other useful piece of information: my site has 1 (and only 1) > admin > user, and he is the only one that does any C, U or D (of > "CRUD")--visitors to my website will only ever read the models, so > there > should never be a time where multiple people will be making > simulaneous > changes that need to be indexed.Hey .. just try it :-) It sounds like you don''t need the ferret server.. keep an eye on your production.log .. you woll see the ferret errors (like specific files in the index could not be found).. i think you will be fine without the server.. and even if you get some errors.. AAF makes it so easy for you to add the server, that it won''t take long :) Ben
On Jun 5, 2007, at 3:18 AM, Myron Marston wrote:> One other useful piece of information: my site has 1 (and only 1) > admin > user, and he is the only one that does any C, U or D (of > "CRUD")--visitors to my website will only ever read the models, so > there > should never be a time where multiple people will be making > simulaneous > changes that need to be indexed.That''s the most useful piece of information :) As long as the admin user doesn''t have multiple windows open doing multiple writes to the ferret index, your app will never experience any concurrency issues.
> As long as the admin > user doesn''t have multiple windows open doing multiple writes to the > ferret index, your app will never experience any concurrency issues.Great, I should be fine without the DRB server. Thanks, guys! -- Posted via http://www.ruby-forum.com/.