Celery 2.1 DocumentationBROKER_PASSWORD = "mypassword" BROKER_VHOST = "myvhost" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[”pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 285 页 | 1.19 MB | 1 年前3
Celery 2.1 DocumentationBROKER_PASSWORD = "mypassword" BROKER_VHOST = "myvhost" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[“pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 463 页 | 861.69 KB | 1 年前3- Celery 2.3 DocumentationBROKER_PASSWORD = "mypassword" BROKER_VHOST = "myvhost" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[”pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 334 页 | 1.25 MB | 1 年前3
- Celery 2.2 DocumentationBROKER_PASSWORD = "mypassword" BROKER_VHOST = "myvhost" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[”pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 314 页 | 1.26 MB | 1 年前3
- Celery 2.2 DocumentationBROKER_PASSWORD = "mypassword" BROKER_VHOST = "myvhost" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[“pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 505 页 | 878.66 KB | 1 年前3
- Celery 2.3 DocumentationBROKER_PASSWORD = "mypassword" BROKER_VHOST = "myvhost" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[“pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 530 页 | 900.64 KB | 1 年前3
- Celery 2.5 Documentation5 BROKER_URL = "amqp://guest:guest@localhost:5672//" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[”pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 400 页 | 1.40 MB | 1 年前3
- Celery 2.4 Documentationexample): BROKER_URL = "amqp://guest:guest@localhost:5672//" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[”pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 395 页 | 1.54 MB | 1 年前3
- Celery 2.4 Documentationexample): BROKER_URL = "amqp://guest:guest@localhost:5672//" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[“pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 543 页 | 957.42 KB | 1 年前3
- Celery 2.5 Documentationexample): BROKER_URL = "amqp://guest:guest@localhost:5672//" 2. Define the backend used to store task metadata and return values: CELERY_RESULT_BACKEND = "amqp" The AMQP backend is non-persistent by default running. The host name and process id of the worker executing the task will be available in the state metadata (e.g. result.info[“pid”]) The global default can be overridden by the CELERY_TRACK_STARTED setting lifetime a task will transition through several possible states, and each state may have arbitrary metadata attached to it. When a task moves into a new state the previous state is forgotten about, but some0 码力 | 647 页 | 1011.88 KB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6