Re: [Django] #2406: [patch] new command for management -- runjobs

[Ian Holsman]

On 24/07/2006, at 11:34 AM, Adrian Holovaty wrote: On 7/23/06, Ian Holsman <[EMAIL PROTECTED]> wrote: this patch doesn't implement 'cron' or anything like that. it just makes it easier to define jobs which the application needs run on a regular basis If your goal is to cut crontab entries from five to one, just create a single script that does the five things you need it to do; then point crontab at it. :) that is what It does, just via signals so I don't end up with what you have in daily_sessions.. a table that doesn't exist  (registration_challenges) being tried to be cleaned, and If I decide to include a new app in my project I wouldn't need to change anything else but settings.py for it to work correctly. (working correctly == archiving/daily maintenance.. not just pretty web screens) django admin has the other features for setting the setting file, python path and other niceties I would  have to repeat in any daily_cleanup lookup I would need. and yes.. I could write my own app which does this, and maintain a separate patch file to apply to django core. but the point of open source is for me to share ... I thought this patch was generic enough and useful enough for others to use. the reason behind it was that I need to send an email out every day in a application, and thought  it would be much easier to just define what the application needs to do in a single spot. (the application code) instead of having it hidden in crontabs. regards Ian Adrian --  Adrian Holovaty holovaty.com | djangoproject.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers -~----------~----~----~----~------~----~------~--~---