1. Let's not call it a cron instance. The idea is that you have one web2py that talks to the users and schedule tasks and you have one or more workers that pickup and run tasks in background. Because there are more than one (in principle) they are different processes.
web2py needs a an interface to allow starting and stopping processes. For the scheduler workers but also for other purposes. Eventually it will but I see it as a different issue. 2. I just added to trunk "repeats=0" means repeat forever. Not intuitive but practical. I am open to alternatives. On Aug 9, 10:51 am, guruyaya <guruy...@gmail.com> wrote: > Basically, I liked what I saw. Few questions: > 1. Will there be a way to start it along with the web2py main app in > the future or I'll have to start a seperate cron instance? > 2. Is there a way to make the task run indefinite? > > On Aug 9, 1:40 pm, Massimo Di Pierro <massimo.dipie...@gmail.com> > wrote: > > > > > > > > >http://www.vimeo.com/27478796
