I deleted #2 to avoid confusion. It works, but only if your model is configured a certain way. It also uses an old way to get the configuration, which is rarely necessary nowadays.
On Mon, Sep 1, 2008 at 7:28 AM, jerry <[EMAIL PROTECTED]> wrote: > > I'm using No. 1, which I consider the (preferably only one) obvious > way. > > No. 2 is too monkey-patching to me. > > No. 3 is not really about auxiliary cron jobs for your application. > > Jerry > > On Sep 1, 7:17 am, Pavel Skvazh <[EMAIL PROTECTED]> wrote: >> There seam to be different ways to get cron jobs with Pylons. >> In my case model has to be accessible in it. >> Found three articles on the wiki describing different approaches, >> which is rather confusing >> >> http://wiki.pylonshq.com/display/pylonscookbook/Cron+jobs+and+command...http://wiki.pylonshq.com/display/pylonscookbook/Running+cron+jobshttp://wiki.pylonshq.com/display/pylonscookbook/Scripts+for+paster+serve >> >> If anyone, who had experience getting this done, can please share a >> best practice on this matter? >> >> Thanks! > > > -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
