You can configure a celery worker on the the same server you run everything else on. Then you can still use celery (which is useful if you ever want to scale to a separate worker machine down the road.
_Nik On 12/10/2012 10:36 AM, Bill Freeman wrote: > > > On Mon, Dec 10, 2012 at 12:44 PM, leonardo <leonardo.s.c...@gmail.com > <mailto:leonardo.s.c...@gmail.com>> wrote: > > Hi, > > I'm deploying a project to validation purpose in Heroku and not > worth paying for a worker to execute background task. > Is there a way to execute background task without celery + rabbitmq ? > > Thanks, > > > Another way to do this is with a cron task to runs a management > command. That still takes a separate task, however, if that costs > money on heroku (I'm unfamiliar with heroku). You could spawn a > thread at some point, making sure that there is just one, and let it > sleep for a fixed time (or set the equivalent alarm signal), waking up > to see if it has any work to do (this can be hard to get right, and > hard to debug). > -- > 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. -- 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.
