Celery 3.1 Documentation
Celery Next Steps Resources User Guide Application Tasks Calling Tasks Canvas: Designing Workflows Workers Guide Periodic Tasks HTTP Callback Tasks (Webhooks) Routing Tasks Monitoring and Management Guide between clients and workers. To initiate a task, a client adds a message to the queue, which the broker then delivers to a worker. A Celery system can consist of multiple workers and brokers, giving way broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers0 码力 | 887 页 | 1.22 MB | 1 年前3Celery 3.1 Documentation
between clients and workers. To initiate a task, a client adds a message to the queue, which the broker then delivers to a worker. A Celery system can consist of multiple workers and brokers, giving way broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' • Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers Cryptographic message signing. Features • Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you what your cluster is doing – in real-time0 码力 | 607 页 | 2.27 MB | 1 年前3Celery v4.0.2 Documentation
Celery Next Steps Resources User Guide Application Tasks Calling Tasks Canvas: Designing Work-flows Workers Guide Daemonization Periodic Tasks Routing Tasks Monitoring and Management Guide Security Optimizing between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers0 码力 | 1042 页 | 1.37 MB | 1 年前3Celery 4.0 Documentation
Celery Next Steps Resources User Guide Application Tasks Calling Tasks Canvas: Designing Work-flows Workers Guide Daemonization Periodic Tasks Routing Tasks Monitoring and Management Guide Security Optimizing between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers0 码力 | 1042 页 | 1.37 MB | 1 年前3Celery v4.0.1 Documentation
Celery Next Steps Resources User Guide Application Tasks Calling Tasks Canvas: Designing Work-flows Workers Guide Daemonization Periodic Tasks Routing Tasks Monitoring and Management Guide Security Optimizing between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers0 码力 | 1040 页 | 1.37 MB | 1 年前3Celery v4.1.0 Documentation
Celery Next Steps Resources User Guide Application Tasks Calling Tasks Canvas: Designing Work-flows Workers Guide Daemonization Periodic Tasks Routing Tasks Monitoring and Management Guide Security Optimizing between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers0 码力 | 1057 页 | 1.35 MB | 1 年前3Celery 4.0 Documentation
between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' • Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers Cryptographic message signing. Features • Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you what your cluster is doing – in real-time0 码力 | 707 页 | 2.63 MB | 1 年前3Celery v4.0.2 Documentation
between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' • Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers Cryptographic message signing. Features • Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you what your cluster is doing – in real-time0 码力 | 707 页 | 2.63 MB | 1 年前3Celery 3.0 Documentation
between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' • Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers Cryptographic message signing. Features • Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you what your cluster is doing – in real-time0 码力 | 703 页 | 2.60 MB | 1 年前3Celery v4.1.0 Documentation
between clients and workers. To initiate a task the client adds a message to the queue, the broker then delivers that message to a worker. A Celery system can consist of multiple workers and brokers, giving broker='amqp://guest@localhost//') @app.task def hello(): return 'hello world' • Highly Available Workers and clients will automatically retry in the event of connection loss or failure, and some brokers Cryptographic message signing. Features • Monitoring A stream of monitoring events is emitted by workers and is used by built-in and external tools to tell you what your cluster is doing – in real-time0 码力 | 714 页 | 2.63 MB | 1 年前3
共 213 条
- 1
- 2
- 3
- 4
- 5
- 6
- 22