Celery 3.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This [http://memcached.org], Redis [http://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 2110 页 | 2.23 MB | 1 年前3
Celery v4.0.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This [http://memcached.org], Redis [http://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='amqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ as0 码力 | 2106 页 | 2.23 MB | 1 年前3
Celery v5.0.5 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2315 页 | 2.14 MB | 1 年前3
Celery v5.0.2 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2313 页 | 2.14 MB | 1 年前3
Celery v5.0.1 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2313 页 | 2.13 MB | 1 年前3
Celery v5.0.0 Documentation[http://memcached.org], Redis [https://redis.io/], RPC (RabbitMQ [http://www.rabbitmq.com/]/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 2309 页 | 2.13 MB | 1 年前3
Celery 3.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. 2.2. Getting Started 21 Celery Documentation, Release 4.0.0 For this example we use the rpc result backend, that sends result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 703 页 | 2.60 MB | 1 年前3
Celery v4.1.0 Documentationto choose from: SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient messages result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ It could look something like this: celeryconfig.py: broker_url = 'pyamqp://' result_backend = 'rpc://' task_serializer = 'json' result_serializer = 'json' accept_content = ['json'] timezone = 'Europe/Oslo'0 码力 | 714 页 | 2.63 MB | 1 年前3
Celery v4.0.1 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This to choose from: SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. For this example we use the rpc result backend, that sends states back as transient messages result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='pyamqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ0 码力 | 705 页 | 2.63 MB | 1 年前3
Celery v4.0.0 Documentationtask failed, the exception and traceback). Results aren’t enabled by default, so if you want to do RPC or keep track of task results in a database you have to configure Celery to use a result backend. This SQLAlchemy/Django ORM, Memcached, Redis, RPC (RabbitMQ/AMQP), and – or you can define your own. 2.2. Getting Started 21 Celery Documentation, Release 4.0.0 For this example we use the rpc result backend, that sends result_backend setting if you choose to use a configuration module): app = Celery('tasks', backend='rpc://', broker='amqp://') Or if you want to use Redis as the result backend, but still use RabbitMQ as0 码力 | 701 页 | 2.59 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













