Right, I was just voting for having the script integrated into web2py outright, so that calling it with maybe a lowercase "-k" would execute a single scheduler process without spawning subprocesses.
On Friday, September 14, 2012 11:57:49 AM UTC-4, Niphlod wrote: > > Scheduler is not useful if managed by a webserver, so forget about -X: > just like softcron, it is meant to be used when the internal webserver is > used, not when web2py is managed by apache & co. > > Having a "master" starting the actual workers is needed to have multiple > workers started with one command through web2py. > If you want to manage the workers through supervisord with the standard > config you have to use this script. > > On Friday, September 14, 2012 5:41:47 PM UTC+2, Yarin wrote: >> >> @Niphlod- I was hoping this "embedded mode" patch was going to become >> part of the 2.0 implementation. I see you added a -X flag to allow for >> launching the scheduler alongside an app, but we can't use this in our >> situation where web2py is running as wsgi under Apache while our scheduler >> processes run under Supervisord. Thoughts? >>> >>> >>> >>> --
