You should be able to fork, but you wouldn't want multiple schedulers
so you'll be limited to 1 worker.
You can setup another app that is another environment of your
production app that only runs the scheduler.
If you get resque:scheduler to run let me know. I've run it on heroku
and it keeps getting killed for some reason then restarted, and it'd
go down sometimes for 20 minuites.
-Jon
On Aug 26, 1:46 pm, Idris wrote:
> We're trying to use resque-scheduler with Heroku, but resque-scheduler
> requires two processes to be running, corresponding to the tasks
> resque:scheduler (which schedules jobs), and resque:work (which pops
> jobs off the queue and performs the work). Given that workers on
> Heroku only run the jobs:work task, how can we get jobs:work to run
> BOTH of these resque jobs? Should we fork inside of the jobs:work
> task? Do heroku workers even support fork?
>
> Thanks,
> Idris
--
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en.
