Re: Cron vs event triggered action

On Sat, Dec 19, 2009 at 06:28:23AM -0800, Tim Daniel wrote: > David, Celery sounds really good, thanks for the tip, I'll have a > deeper look into it as soon as I've got some time, if I can't get it > one question: Is it capable of running on every web server > that supports Python? Well, it's

Re: Cron vs event triggered action

Hello Tim, On Dec 19, 6:28 am, Tim Daniel wrote: > Brian & Creecode Django Custom management commands are really the same > as this: > > from django.core.management import setup_environ > import settings > setup_environ(settings) > > or am I wrong? I'm just running the

Re: Cron vs event triggered action

David, Celery sounds really good, thanks for the tip, I'll have a deeper look into it as soon as I've got some time, if I can't get it up for this project I'll study it's details and put it up later maybe for a new release or a new project. For what I've seen until now it seems to be perfect,

Re: Cron vs event triggered action

Tim Daniel wrote: > So how can I implement solution B? Is there a posibility to create a > cron on a user action that executes only one time? > > NOTE: I don't want to rely on a thread that should stay alive for two > hours ore more inside the server memory. Well, celery uses a "celeryd"

Re: Cron vs event triggered action

Just to throw it out there... forget about trying to make something happen every ten minutes; or whatever your margin for error is. Instead focus on just testing to see whether two hours have passed when you come to use it. Either lazy (C), or diligent (D)... Solution C: Do nothing at all until

Re: Cron vs event triggered action

I deployed on on EC2 using apache + mod_wsgi and it worked. My APS setup is as follow: def start_notificator(): sched = Scheduler() sched.add_interval_job(notificator.send_notification, seconds=10) sched.daemonic = True t = Thread(target=fire_scheduler,

Re: Cron vs event triggered action

Have you consider the linux at command instead of cron? Example: echo "touch /home/mateusz/my.name.is.at" | at 02:30 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To

Re: Cron vs event triggered action

Hello all, On Dec 14, 3:57 pm, Brian Neal wrote: > http://docs.djangoproject.com/en/dev/howto/custom-management-commands/ Thanks for answering Brian! Saved me having to do that part myself! :-) Tim, I did it the python script way at first but have been moving over the the

Re: Cron vs event triggered action

On Dec 14, 12:27 pm, Tim Daniel wrote: > ... > > Creecode what do you mean with "custom management commands"? I just > wrote a simple python script that can be called from bash like this > python myscript.py, inside it I set up the enviroment to be able to > call my

Re: Cron vs event triggered action

On Mon, Dec 14, 2009 at 5:12 PM, Guilherme Cavalcanti wrote: > If are you going to choose A, take a look on Advanced Python Schedule > (http://apscheduler.nextday.fi/). It's a python module that let you > schedule some script to be executed periodically, it really makes

Re: Cron vs event triggered action

If are you going to choose A, take a look on Advanced Python Schedule (http://apscheduler.nextday.fi/). It's a python module that let you schedule some script to be executed periodically, it really makes the job easier. On Dec 14, 3:27 pm, Tim Daniel wrote: > Thanks for

Re: Cron vs event triggered action

Thanks for answering, I think I'm going to go with 'A' too. Guilherme I've had already looked after django-cron but don't know why but it doesn't seem to work well, I've tried to increment a simple counter in the database every 30 seconds and it doesn't work(using the development server with

Re: Cron vs event triggered action

Tim, recently I've used the solution A too. Take a look on these plugins: http://code.google.com/p/django-cron/ http://code.google.com/p/django-jits/ http://github.com/jtauber/django-notification/blob/master/docs/usage.txt Pay attention specially on django-jits, it uses a little different

Re: Cron vs event triggered action

Hello Tim, On Dec 12, 2:58 pm, Tim Daniel wrote: > Solution A: Have a datetime field with an expiry date and say every 10 > minutes a cron job checks the DB table for expired entries and > performs the programed action. I've used solution A in combination with custom