How to install Celery on Django and Create a Periodic Task

This post explains how to set up Celery with Django, using RabbitMQ as a message broker.

It also explains how to create a Periodic Task

In particular, I used Celery 3.1.8, Django 1.6.2 and Django-Celery 3.1.1.

The Broker RabbitMQ

First, we need to choose what is called a Message Broker, required by Celery in order to send and receive messages. Here we will use RabbitMQ, which is feature-complete, stable, durable and easy to install. Moreover, it is the default broker so it does not require additional configuration :-)

Check out how to install it for your particular system here. If you are using Mac OS X you can install it with homebrew (and if you want to install first homebrew… check this post):

$ brew install rabbitmq

The RabbitMQ server scripts are installed into /usr/local/sbin. This is not automatically added to your path, so open or edit a .procfile in your home folder

$ touch ~/.procfile

$ vi ~/.procfile

and add the following line

export PATH=$PATH:/usr/local/sbin

The server can then be started with

$ sudo rabbitmq-server -detached

Where the -detached flag indicates the server to run in the background. To stop the server use

$ sudo rabbitmqctl stop

You can find a detailed description on how to use RabbitMQ with Celerey here.

After installing RabbitMQ we need to create a RabbitMQ user, a virtual host and allow that user to access the virtual host. We also start the server before that:

$ sudo rabbitmq-server -detached

$ sudo rabbitmqctl add_user myuser mypassword

$ sudo rabbitmqctl add_vhost myvhost

$ sudo rabbitmqctl set_permissions -p myvhost myuser “.*” “.*” “.*”

Then, open your Django project file and configure RabbitMQ by adding the lines:

BROKER_URL = “amqp://myuser:mypassword@localhost:5672/myvhost”

This tells celery, where your broker (your queue) is loacated. Here, we are running Celery at the same machine as RabbitMQ and using the localhost to find it.


Celery is on the Python Package Index (PyPi), and can be easily installed with pip or easy_install. Remember to activate first your virtual environment (if you want to install Virtualenv to create a virtual enviroment check this post).

$ pip install celery

Next, add this package to your requirements.txt file, so that both the production environment and the development environment on your local machine will use it. Recall that you can check the packages used by the current environment with

$ pip freeze

You will see that you have installed celery, pytz, billiard, kombu, anyjson and amqp. Write them all on your requirements file. You can also write them directly by using

$ pip freeze > requirements.txt

Now, we need to cretate a Celery instance, called a Celery app. Create a file at the same level of your file:

$ touch myprojectfolder/myproject/

And write the following code:

Then, to ensure that the app is loaded when Django starts, you need to import this app in the file. Open the file that is at the same level than the and files and write:

from __future__ import absloute_import

from .celery import app as celery_app

Moreover, for security purposes, you should specify a list of accepted content-types in the file:


which for the example here, we set to json content type. Then, we need to specify the task serializer accordingly:



Finanly, we can specify the time zone we are in:

CELERY_TIMEZONE = ‘Europe/Madrid’

Note: In Celery 3.0+ the setting CELERY_ENABLE_UTC is enabled by default (it is set to True). This setting, if enabled, makes the dates and times in messages to be converted to use the UTC timezone.


The django-celery package defines a result backend to keep track of the state of the tasks. To install it:

$ pip install django-celery

remember to include it in your requirements file. Then, add it to your installed apps in your settings file:



Next, we need to create the tables for the database of this app, which can be managed by South (If you don’t have South installed… what are you waiting for? It is an extremely useful package! Install it via pip install South). Migrate django-celery and sync the rest of the database with

$ python migrate djcelery

$ python syncdb

As we have indicated Celery to use our file, we can configure Celery to use the django-celery backend by adding this line into the file:

from __future__ import absolute_import CELERY_RESULT_BACKEND=’djcelery.backends.database:DatabaseBackend’ CELERYBEAT_SCHEDULER = ‘djcelery.schedulers.DatabaseScheduler’

Create a Periodic Task

One thing you might want to use in your project is a Scraper, which is, for example, an aplication that runs periodicaly at night to update some data for your web site.

Choose or create an application in your Django project to include the Scraper. Then, create and edit the file myapp/utils/ (note: you must have an empty file inside the utils folder). The file must contain a function that performs your desired operations, like accessing an API and modifying your database.

In this example, we just write:

def scraper_example(a, b):

    return a + b

Then, create the file myapp/ and edit it:

Here, we have created a periodic task that will run every minute, and that writes into the logger two messages indiciating the begining and the end of the task, and also calls our scraper function.

Run it!

Ok, so we have our Periodic Task created, but how can we run it?? First start your RabbitMQ server:

$ sudo rabbitmq-server -detached

Next, start a Celery worker

$ python celeryd –verbosity=2 –loglevel=DEBUG

If the installation is correct, you should see at the top of the text displayed something like

transport: amqp://myuser@localhost:5672/myvhost

results: djcelery.backends.database:DatabaseBackend

And a list of the application tasks:

  .  celery.backend_cleanup
  .  ……etc
  .  myapp.tasks.scraper_example

Next, open a new tab and start celerybeat, which will send the registered tasks periodically to RabbitMQ:

$ python celerybeat –verbosity=2 –loglevel=DEBUG

If you go back to the Celery worker tab, you will see the results of your tasks :-)

And finally, open another tab and start your Django developement server:

$ python runserver

Note: Beat needs to store the last run times of the tasks in a local database file, which by default is celerybeat-schedule.db and it’s placed at the same level of your file. If you are using Git as version control, you should include this file into your gitignore file.

Please, give a +1 if you liked it! Thanks!


Please, add +Marina Mele in your comments. This way I will get a notification email and I will answer you as soon as possible! :-)