Contributing Community Code of Conduct Reporting a Bug Coding Style Tutorials Using Celery with Redis/Database as the messaging queue. Tutorial: Creating a click counter using carrot and celery Frequently Asked result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Webhooks Your tasks can also be HTTP callbacks Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide gives an overview

Configuration and defaults Example configuration file Concurrency settings Task result backend settings Database backend settings AMQP backend settings Cache backend settings Tokyo Tyrant backend settings Redis celeryd as a daemon Tutorials Tutorials and resources from the community Using Celery with Redis/Database as the messaging queue. Tutorial: Creating a click counter using carrot and celery Frequently Asked result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Webhooks Your tasks can also be HTTP callbacks

result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your tasks can naming and relative imports Decorating tasks Task States Result Backends AMQP Result Backend Database Result Backend Built-in States PENDING STARTED SUCCESS FAILURE RETRY REVOKED Custom states How Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide gives an overview

result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your tasks can naming and relative imports Decorating tasks Task States Result Backends AMQP Result Backend Database Result Backend Built-in States PENDING STARTED SUCCESS FAILURE RETRY REVOKED Custom states Creating Avoid launching synchronous subtasks Performance and Strategies Granularity Data locality State Database transactions Example blog/models.py blog/views.py blog/tasks.py This guide gives an overview

. . . . . . . . . . . . . . . . . . . . . . . . 93 7 Tutorials 95 7.1 Using Celery with Redis/Database as the messaging queue. . . . . . . . . . . . . . . . . . . . . . . 95 7.2 Tutorial: Creating a result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Web- hooks Your tasks can also be HTTP launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions • Example – blog/models.py – blog/views.py – blog/tasks.py This guide gives an overview

Documentation Installation Brokers Using RabbitMQ Using Redis Using SQLAlchemy Using the Django Database Using MongoDB Using CouchDB Using Beanstalk First steps with Celery Choosing your Broker Creating result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Webhooks Your tasks can several message transport alternatives. Using RabbitMQ Using Redis Using SQLAlchemy Using the Django Database Using MongoDB Using CouchDB Using Beanstalk © Copyright 2009-2011, Ask Solem & Contributors. index

result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, AMQP (high performance). Web- hooks Your tasks can also be HTTP launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions 2.1.1 Basics A task is a class that encapsulates a function and its execution options Release 2.0.3 (stable) In the view where the comment is posted, we first write the comment to the database, then we launch the spam filter task in the background. blog/views.py from django import forms

result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Web- hooks Your tasks and relative imports • Decorating tasks • Task States – Result Backends * AMQP Result Backend * Database Result Backend – Built-in States * PENDING * STARTED * SUCCESS * FAILURE * RETRY * REVOKED – launching synchronous subtasks • Performance and Strategies – Granularity – Data locality – State – Database transactions • Example – blog/models.py – blog/views.py – blog/tasks.py This guide gives an overview

. . . . . . . . . . . . . . . . . . . . . . . 97 7 Tutorials 103 7.1 Using Celery with Redis/Database as the messaging queue. . . . . . . . . . . . . . . . . . . . . . . 103 7.2 Debugging Tasks Remotely result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Web- hooks Your tasks and relative imports • Decorating tasks • Task States – Result Backends * AMQP Result Backend * Database Result Backend – Built-in States * PENDING * STARTED * SUCCESS * FAILURE * RETRY * REVOKED –

. . . . . . . . . . . . . . . . . . . . . . . 121 7 Tutorials 127 7.1 Using Celery with Redis/Database as the messaging queue. . . . . . . . . . . . . . . . . . . . . . . 127 7.2 Debugging Tasks Remotely result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Tokyo Tyrant, Cassandra, or AMQP (message notification). Web- hooks Your tasks Configuration Configuration is easy, set the transport, and configure the location of your Redis database: BROKER_URL = "redis://localhost:6379/0" Where the URL is in the format of: redis://userid:p