Thanks for the reply Morten. Repeated_job looks like just the ticket
and a very elegant and simple solution too.

One further question: I presume that this will require 1 worker to
function and that this will negate the need for the Cron add-on? Will
calling rake::cron every 15 minutes via this method hit any sort of
limiter designed to stop people circumnavigating the paid hourly Cron
add-on? In other words: how does the business side of this work? :)

Thanks again,

Russell.


On Jul 27, 10:41 pm, Morten Bagai <[email protected]> wrote:
> Hi Russell,
>
> One of our engineers made this fork of DJ that I believe does what you 
> want:http://github.com/ddollar/repeated_job. Let me know if there's anything 
> else we can help with. We're looking forward to having you on our platform.
>
> Best,
>
> Morten
>
> On Jul 27, 2010, at 9:15 AM, Russell Quinn wrote:> I'm migrating an iPhone 
> app backend server from Brightbox to Heroku.
> > One thing the app does is perform a rake task every 15 minutes to
> > check for various things including sending Push Notifications in
> > batches.
>
> > I understand that this rake task should probably be run in a Delayed
> > Job task, but how do I put one new Delayed Job task in the queue every
> > 15 minutes? i.e. There is no user task performed to trigger the
> > creation of new jobs, rather they need to be created every 15 minutes.
>
> > Thanks,
>
> > Russell.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Heroku" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/heroku?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.

Reply via email to