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 Unit Testing Tutorials External tutorials and resources 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, AMQP (high performance). Web- hooks Your tasks can also be HTTP to use celery with your Django project. 1. Add celery to INSTALLED_APPS. 2. Create the celery database tables: $ python manage.py syncdb 3. Configure celery to use the AMQP user and virtual host we available, please see the configuration directive reference. Note: If you’re using SQLite as the Django database back-end, celeryd will only be able to process one task at a time, this is because SQLite doesn’t

result store backend. You can wait for the result, retrieve it later, or ignore it. Result Stores Database, MongoDB, Redis, Cassandra, or AMQP (message notification). Web- hooks Your tasks can also be 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 Installation Configuration Celery needs to know the location of your database, which should be the usual SQLAlchemy connection string, but with ‘sqla+’ prepended to it: BROKER_URL = "sqla+sqlite:///celerydb

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

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

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, Cassandra, or AMQP (message notification). Webhooks Your tasks can also be HTTP several message transport alternatives. Using RabbitMQ Using Redis Using SQLAlchemy Using the Django Database Using MongoDB Using CouchDB Using Beanstalk © Copyright 2009-2012, 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, Cassandra, or AMQP (message notification). Webhooks Your tasks can Strategies Example Executing Tasks Basics ETA and countdown Expiration Serializers Connections and connection timeouts. Routing options AMQP options Workers Guide Starting the worker Stopping the worker 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

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 Strategies Example Executing Tasks Basics ETA and countdown Expiration Serializers Connections and connection timeouts. Routing options AMQP options Workers Guide Starting the worker Stopping the worker 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

. . . . . . . . . . . . . . . . . . . . . . . 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 –

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 Strategies Example Executing Tasks Basics ETA and countdown Expiration Serializers Connections and connection timeouts. Routing options AMQP options Workers Guide Starting the worker Stopping the worker