Celery 1.0 Documentationaccess to the task function to be able to run it. Put them in the tasks module of your Django application. The worker server will automatically load any tasks.py file for all of the applications listed wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. 18 Chapter 2. User Guide Celery Documentation to exchanges, a queue binds to an exchange with a routing key. Let’s look at an example: Our application has a lot of tasks, some process video, others process images, and some gather collective intelligence0 码力 | 123 页 | 400.69 KB | 1 年前3
Celery 1.0 Documentationaccess to the task function to be able to run it. Put them in the tasks module of your Django application. The worker server will automatically load any tasks.py file for all of the applications listed wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks to exchanges, a queue binds to an exchange with a routing key. Let’s look at an example: Our application has a lot of tasks, some process video, others process images, and some gather collective intelligence0 码力 | 221 页 | 283.64 KB | 1 年前3
Celery 2.5 Documentationmeta={"current": i, "total": len(filenames)}) Here we created the state “PROGRESS”, which tells any application aware of this state that the task is currently in progress, and also where it is in the process wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks queue binds to an exchange with a routing key. Let’s look at an example: Let’s pretend we have an application with lot of different tasks: some process video, others process images, and some gather collective0 码力 | 400 页 | 1.40 MB | 1 年前3
Celery 2.0 Documentationwait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks to exchanges, a queue binds to an exchange with a routing key. Let’s look at an example: Our application has a lot of tasks, some process video, others process images, and some gather collective intelligence but you need to experiment to find the values that works best for you as this varies based on application, work load, task run times and other factors. 2.3.5 Time limits A single task can potentially0 码力 | 165 页 | 492.43 KB | 1 年前3
Celery 2.3 Documentationmeta={"current": i, "total": len(filenames)}) Here we created the state “PROGRESS”, which tells any application aware of this state that the task is currently in progress, and also where it is in the process wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. 2.2. Tasks 29 Celery Documentation, Release queue binds to an exchange with a routing key. Let’s look at an example: Let’s pretend we have an application with lot of different tasks: some process video, others process images, and some gather collective0 码力 | 334 页 | 1.25 MB | 1 年前3
Celery 2.0 Documentationwait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks to exchanges, a queue binds to an exchange with a routing key. Let’s look at an example: Our application has a lot of tasks, some process video, others process images, and some gather collective intelligence but you need to experiment to find the values that works best for you as this varies based on application, work load, task run times and other factors. Time limits A single task can potentially run forever0 码力 | 284 页 | 332.71 KB | 1 年前3
Celery 2.5 Documentationmeta={"current": i, "total": len(filenames)}) Here we created the state “PROGRESS”, which tells any application aware of this state that the task is currently in progress, and also where it is in the process wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks queue binds to an exchange with a routing key. Let’s look at an example: Let’s pretend we have an application with lot of different tasks: some process video, others process images, and some gather collective0 码力 | 647 页 | 1011.88 KB | 1 年前3
Celery 2.2 Documentationmeta={"current": i, "total": len(filenames)}) Here we created the state “PROGRESS”, which tells any application aware of this state that the task is currently in progress, and also where it is in the process wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks queue binds to an exchange with a routing key. Let’s look at an example: Let’s pretend we have an application with lot of different tasks: some process video, others process images, and some gather collective0 码力 | 314 页 | 1.26 MB | 1 年前3
Celery 2.3 Documentationmeta={"current": i, "total": len(filenames)}) Here we created the state “PROGRESS”, which tells any application aware of this state that the task is currently in progress, and also where it is in the process wait for it to finish. We have a Django blog application allowing comments on blog posts. We’ll describe parts of the models/views and tasks for this application. blog/models.py The comment model looks queue binds to an exchange with a routing key. Let’s look at an example: Let’s pretend we have an application with lot of different tasks: some process video, others process images, and some gather collective0 码力 | 530 页 | 900.64 KB | 1 年前3
Celery 3.1 DocumentationStarted Introduction to Celery Brokers First Steps with Celery Next Steps Resources User Guide Application Tasks Calling Tasks Canvas: Designing Workflows Workers Guide Periodic Tasks HTTP Callback Tasks Features Framework Integration Quickjump Installation Brokers Broker Instructions Experimental Transports Broker Overview First Steps with Celery Choosing a Broker Installing Celery Application Running Results Configuration Where to go from here Troubleshooting Next Steps Using Celery in your Application Calling Tasks Canvas: Designing Workflows Routing Remote Control Timezone Optimization What to0 码力 | 887 页 | 1.22 MB | 1 年前3
共 51 条
- 1
- 2
- 3
- 4
- 5
- 6













