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, args=[sched], name="Notificator")
t.setDaemon(True)
t.start()
notificator.send_notification() is responsible for searching expired
"events" entries on database and sending them via e-mail/twitter/sms.
fire_scheduler just starts the scheduler (sched, defined up there) and
sets up some configs.
On Dec 14, 7:23 pm, Javier Guerra <jav...@guerrag.com> wrote:
> On Mon, Dec 14, 2009 at 5:12 PM, Guilherme Cavalcanti
>
> <guiocavalca...@gmail.com> 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 the
> > job easier.
>
> sounds really great; but, from the very first paragraph:
>
> APScheduler is a light but powerful in-process task scheduler
>
> the "in-process" part can make it very powerful while easy to use; but
> can it run _after_ Django has returned the response to the web server?
> IOW: does APScheduler run 'outside' the request-process-response
> loop? or maybe it works with flup but not mod_wsgi, or the other way
> around?
>
> in any case, it's worth some checking
>
> --
> Javier
--
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 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.
