Celery 3.1 Documentationrabbitmq.com/access-control.html. If supported by your broker backend, you can enable end-to-end SSL encryption and authentication using BROKER_USE_SSL. 2.3. User Guide 135 Celery Documentation, Release 3 You can enable this using the BROKER_USE_SSL setting. It is also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 607 页 | 2.27 MB | 1 年前3
Celery 3.1 Documentationrabbitmq.com/access- control.html. If supported by your broker backend, you can enable end-to-end SSL encryption and authentication using BROKER_USE_SSL. Client In Celery, “client” refers to anything that sends RabbitMQ). You can enable this using the BROKER_USE_SSL setting. It is also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 887 页 | 1.22 MB | 1 年前3- Celery 2.1 DocumentationYou can enable this using the BROKER_USE_SSL setting. It is also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 285 页 | 1.19 MB | 1 年前3
- Celery 2.1 DocumentationRabbitMQ). You can enable this using the BROKER_USE_SSL setting. It is also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 463 页 | 861.69 KB | 1 年前3
- Celery 2.3 DocumentationRabbitMQ). You can enable this using the BROKER_USE_SSL setting. It is also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 334 页 | 1.25 MB | 1 年前3
- Celery 2.2 DocumentationYou can enable this using the BROKER_USE_SSL setting. It is also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 314 页 | 1.26 MB | 1 年前3
- Celery 3.0 Documentationrabbitmq.com/access-control.html. If supported by your broker backend, you can enable end-to-end SSL encryption and authentication using broker_use_ssl. Client In Celery, “client” refers to anything that sends RabbitMQ). You can enable this using the broker_use_ssl setting. It’s also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 703 页 | 2.60 MB | 1 年前3
- Celery v4.0.1 Documentationrabbitmq.com/access- control.html. If supported by your broker backend, you can enable end-to-end SSL encryption and authentication using broker_use_ssl. Client In Celery, “client” refers to anything that sends RabbitMQ). You can enable this using the broker_use_ssl setting. It’s also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 1040 页 | 1.37 MB | 1 年前3
- Celery v4.0.2 Documentationrabbitmq.com/access- control.html. If supported by your broker backend, you can enable end-to-end SSL encryption and authentication using broker_use_ssl. Client In Celery, “client” refers to anything that sends RabbitMQ). You can enable this using the broker_use_ssl setting. It’s also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 1042 页 | 1.37 MB | 1 年前3
- Celery v4.1.0 Documentationrabbitmq.com/access-control.html. If supported by your broker backend, you can enable end-to-end SSL encryption and authentication using broker_use_ssl. 144 Chapter 2. Contents Celery Documentation, Release RabbitMQ). You can enable this using the broker_use_ssl setting. It’s also possible to add additional encryption and security to messages, if you have a need for this then you should contact the Mailing list0 码力 | 714 页 | 2.63 MB | 1 年前3
共 47 条
- 1
- 2
- 3
- 4
- 5