see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority' **** --- . broker: amqp://guest@localhost:5672// - ** ---------- . app: __main__:0x1012d8590 - ** ---------- . concurrency: 8 (processes) - ** ---------- . events: OFF (enable -E to monitor 2) >>> res.get(timeout=1) 4 You can find the task’s id by looking at the id attribute: >>> res.id d6b3aea2-fb9b-4ebc-8da4-848818db9114 You can also inspect the exception and traceback if the task raised

see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority' **** --- . broker: amqp://guest@localhost:5672// - ** ---------- . app: __main__:0x1012d8590 - ** ---------- . concurrency: 8 (processes) - ** ---------- . events: OFF (enable -E to monitor 2) >>> res.get(timeout=1) 4 You can find the task’s id by looking at the id attribute: >>> res.id d6b3aea2-fb9b-4ebc-8da4-848818db9114 You can also inspect the exception and traceback if the task raised

sudo apt-get install rabbitmq-server Or, if you want to run it on Docker execute this: $ docker run -d -p 5672:5672 rabbitmq When the command completes, the broker will already be running in the background information about using Redis: Using Redis If you want to run it on Docker execute this: $ docker run -d -p 6379:6379 redis Other brokers In addition to the above, there are other experimental transport see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority'

sudo apt-get install rabbitmq-server Or, if you want to run it on Docker execute this: $ docker run -d -p 5672:5672 rabbitmq When the command completes, the broker will already be running in the background information about using Redis: Using Redis If you want to run it on Docker execute this: $ docker run -d -p 6379:6379 redis Other brokers In addition to the above, there are other experimental transport see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority'

sudo apt-get install rabbitmq-server Or, if you want to run it on Docker execute this: $ docker run -d -p 5672:5672 rabbitmq When the command completes, the broker will already be running in the background information about using Redis: Using Redis If you want to run it on Docker execute this: $ docker run -d -p 6379:6379 redis Other brokers In addition to the above, there are other experimental transport see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority'

see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority' **** --- . broker: amqp://guest@localhost:5672// - ** ---------- . app: __main__:0x1012d8590 - ** ---------- . concurrency: 8 (processes) - ** ---------- . events: OFF (enable -E to monitor 2) >>> res.get(timeout=1) 4 You can find the task’s id by looking at the id attribute: >>> res.id d6b3aea2-fb9b-4ebc-8da4-848818db9114 You can also inspect the exception and traceback if the task raised

sudo apt-get install rabbitmq-server Or, if you want to run it on Docker execute this: $ docker run -d -p 5672:5672 rabbitmq When the command completes, the broker will already be running in the background information about using Redis: Using Redis If you want to run it on Docker execute this: $ docker run -d -p 6379:6379 redis Other brokers In addition to the above, there are other experimental transport see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority'

see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority' [Configuration] -- * - **** --- . broker: amqp://guest@localhost:5672// - ** ---------- . app: __main__:0x1012d8590 - ** ---------- . concurrency: 8 (processes) - ** ---------- . events: OFF (enable -E to monitor 2) >>> res.get(timeout=1) 4 You can find the task’s id by looking at the id attribute: >>> res.id d6b3aea2-fb9b-4ebc-8da4-848818db9114 You can also inspect the exception and traceback if the task raised

see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority' [Configuration] -- * - **** --- . broker: amqp://guest@localhost:5672// - ** ---------- . app: __main__:0x1012d8590 - ** ---------- . concurrency: 8 (processes) - ** ---------- . events: OFF (enable -E to monitor 2) >>> res.get(timeout=1) 4 You can find the task’s id by looking at the id attribute: >>> res.id d6b3aea2-fb9b-4ebc-8da4-848818db9114 You can also inspect the exception and traceback if the task raised

see Configuration and defaults. To demonstrate the power of configuration files, this is how you’d route a misbehaving task to a dedicated queue: celeryconfig.py: task_routes = { 'tasks.add': 'low-priority' [Configuration] -- * - **** --- . broker: amqp://guest@localhost:5672// - ** ---------- . app: __main__:0x1012d8590 - ** ---------- . concurrency: 8 (processes) - ** ---------- . events: OFF (enable -E to monitor 2) >>> res.get(timeout=1) 4 You can find the task’s id by looking at the id attribute: >>> res.id d6b3aea2-fb9b-4ebc-8da4-848818db9114 You can also inspect the exception and traceback if the task raised