Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Explicitly pass the Celery instance name. #972

Merged
merged 1 commit into from

2 participants

@alexpearce

When starting a Celery worker module, it is assumed that the Celery instance within the module is called app. This is not the case in the Celery pattern, where it is called celery, and so must be explicitly referenced.

@alexpearce alexpearce Explicitly pass the Celery instance name.
When starting a Celery worker module, it is assumed that the Celery instance within the module is called `app`. This is not the case in the Celery pattern, where it is called `celery`, and so must be explicitly referenced.
3d6de4d
@mitsuhiko mitsuhiko merged commit 11003d0 into mitsuhiko:master
@alexpearce alexpearce deleted the unknown repository branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 5, 2014
  1. @alexpearce

    Explicitly pass the Celery instance name.

    alexpearce authored
    When starting a Celery worker module, it is assumed that the Celery instance within the module is called `app`. This is not the case in the Celery pattern, where it is called `celery`, and so must be explicitly referenced.
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 1 deletion.
  1. +1 −1  docs/patterns/celery.rst
View
2  docs/patterns/celery.rst
@@ -86,7 +86,7 @@ disappointed to learn that your ``.wait()`` will never actually return.
That's because you also need to run celery. You can do that by running
celery as a worker::
- $ celery -A your_application worker
+ $ celery -A your_application.celery worker
The ``your_application`` string has to point to your application's package
or module that creates the `celery` object.
Something went wrong with that request. Please try again.