On Jan 4, 9:33 pm, Mark Jones <mark0...@gmail.com> wrote: > You need a process running outside the bounds of the webserver that > reads the database every so often, and then sleeps with a wakeup every > so often, and a list of when things "expire". It updates the > database, the webpage reflects the update. > > You could of course do this via a wget driven by crontab, so that all > the logic is on the webserver.....
Bleurgh. A much better way to keep the logic in one place is to write a custom manage.py command, and have the crontab call that. See the (unfortunately very brief) documentation on how to do that here: http://docs.djangoproject.com/en/dev/howto/custom-management-commands/ However, as Ben implies above, the situation as described by the OP doesn't necessarily require any kind of schedule-based updates at all. If all you need is to work out which projects are not expired as of now, why not simply get that list by querying for all projects with start time > now minus 2 hours? Or, if you like, on creation of a project automatically set expiration time to now + 2 hours, then get your list by querying for all projects with expiration time < now. -- DR. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
