[Rails] Re: Rails way to do long running tasks

I would highly recommend using delayed_job ( http://github.com/tobi/delayed_job/tree/master). We've recently integrated this into the BioCatalogue (http://www.biocatalogue.org) to great effect. This is what GitHub use I believe (http://github.com/blog/197-the-new-queue ). Useful blog post that wal

[Rails] Re: Rails way to do long running tasks

Thanks a lot for the pointers and the great suggestions. I really do find BackgrounDrb too heavy for my implementation - and think the gems you described make sense. Spawn plugin and Javan-whenever is great. And there is a Railscast that is really good in explaining: http://railscasts.com/epi

[Rails] Re: Rails way to do long running tasks

@Bharat, Can you give brief why to use javan instead backgroundrb ? As, i am using backgroundrb for heavy upload duties and it works fine for me. - Sandip R~ On Sun, Jun 7, 2009 at 11:26 PM, Bharat wrote: > > Two pointers from personal experience: > > 1. Don't use backgroundrb for asynchronou

[Rails] Re: Rails way to do long running tasks

Two pointers from personal experience: 1. Don't use backgroundrb for asynchronous processing 2. Do use javan-whenever to automate your cron jobs (available on Github) Bharat --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Googl

[Rails] Re: Rails way to do long running tasks

For emails, the simplest way is to set up a local MTA (postfix, for instance) and send the mail to that. The MTA takes care of the hard part delivering the mail as needed. For more general things, there are some gems that let you set up cron- like tasks, or you can just call a rake task from plai

[Rails] Re: Rails way to do long running tasks

Chris wrote: >* how to send emails without making the user wait Either Thread.new{}, or a plugin called Spawn. You need the latter if your e-mails call templates which in turn call ActiveRecord. A separate thread requires a separate database connection, and Spawn handles this. >*