Celery 3.1.9 Django integration, specifying settings file, without using djcelery

Question

I began using celery 3.1.9 today with Django. This newer version has a tighter integration with django that removes the need to using django-celery.

I use multiple settings files and I was wondering if there was an easy way to specify which settings file to use when initializing the celery worker?

With djcelery it is quite simply since it uses the manage.py commands.

I naively tried to check if

settings.DEBUG was true in the celery.py file, but of course that failed because the settings were not loaded yet!

THe next step is to dive into the django-celery source and emulate what they are doing, but before that, I was hoping someone had found an easy way of achieving this?

Thank you

Have you read the Getting started with Django? It has changed since when django-celery was in use. celery.readthedocs.org/en/latest/django/… — olofom
– olofom, Commented Feb 26, 2014 at 23:32
@oloform: Yes, the docs only explain how to setup when you have one settings file. — Bentley4
– Bentley4, Commented Mar 3, 2014 at 14:19

Pablo Guerrero · Accepted Answer · 2017-01-03 00:36:03Z

7

A solution is to use environment variables.

In celery.py

Instead of

os.environ.setdefault('DJANGO_SETTINGS_MODULE', 'proj.settings')

use

os.environ.setdefault('DJANGO_SETTINGS_MODULE', '{0}'.format(get_env_setting('DJANGO_SETTINGS_MODULE')))

With get_env_setting defined as:

from os import environ
from django.core.exceptions import ImproperlyConfigured

# https://github.com/twoscoops/django-twoscoops-project/blob/develop/project_name/project_name/settings/production.py#L14-L21
def get_env_setting(setting):
    """ Get the environment setting or return exception """
    try:
        return environ[setting]
    except KeyError:
        error_msg = "Set the %s env variable" % setting
        raise ImproperlyConfigured(error_msg)

You could put that in your settings.base.py e.g. .

Then set the DJANGO_SETTINGS_MODULE environment variable for each environment. E.g. set it to my_project.settings.production in the production environment. This variable can by permanently set by adding the following line to ~/.bashrc:

export DJANGO_SETTINGS_MODULE=my_project.settings.production

edited Jan 3, 2017 at 0:36

Pablo Guerrero

1,1341 gold badge16 silver badges24 bronze badges

answered Mar 4, 2014 at 14:01

Bentley4

11.1k27 gold badges89 silver badges141 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Chitrank Dixit Over a year ago

This solution is not working for me, It throws the error django.core.exceptions.ImproperlyConfigured: Set the DJANGO_SETTINGS_MODULE env variable

Bentley4 Over a year ago

Seems like you didn't set the DJANGO_SETTINGS_MODULE environment variable (point to your settings module). Also, this is just an idea for one implementation, the idea is about using an environment variable to decide what settings module to load.

lkiss80 · Accepted Answer · 2014-09-29 18:02:04Z

1

When initializing the celery worker on the command line, just set the environment variable prior to the celery command.

DJANGO_SETTINGS_MODULE='proj.settings' celery -A proj worker -l info

answered Sep 29, 2014 at 18:02

lkiss80

7769 silver badges8 bronze badges

Collectives™ on Stack Overflow

Celery 3.1.9 Django integration, specifying settings file, without using djcelery

2 Answers 2

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related