On Wed, Sep 16, 2015 at 2:34 PM, Erol Merdanović <zasebn...@gmail.com> wrote: > Hello Vijay > > The differences are > 1. Celery message and our message has different format > 2. Celery uses custom queues > > Is this correct? >
Yep. Celery is a distributed task system which can use AMQP as transport, but by default it just uses simple direct exchanges. If you are using AMQP for something more specialized, like a fanout or topic exchange, you can configure this for celery. It is still all about running tasks though. This page in the celery docs describes how celery uses AMQP, and briefly discusses the format: http://celery.readthedocs.org/en/latest/userguide/routing.html Implementing your worker processes as a management command is sensible, I would use something like supervisord or circusd to manage the processes. You should integrate restarting the workers in to the deployment scripts that update your web server code. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFHbX1KNGkmSSWSH25N_vsFmq2VOKc3A%2BVAA2VGXKdu--r7%3DDw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
