The worst part about Django + Celery is deployment. It's very challenging to manage deploying celery with a taks worker like rabbitmq or redis. Do you have any thoughts on that? It would be great if you could do a follow up video with a single project with celery that you deploy to a cloud service like AWS (say ElasticBeanstalk) or any alternative service even GCloud. Thanks for your work on this!
Dockerize and store the state in a database so the workers will still continue to work on the last remaining tasks so that when you update or deploy your django version it will store the last state and continue.
The worst part about Django + Celery is deployment. It's very challenging to manage deploying celery with a taks worker like rabbitmq or redis. Do you have any thoughts on that? It would be great if you could do a follow up video with a single project with celery that you deploy to a cloud service like AWS (say ElasticBeanstalk) or any alternative service even GCloud. Thanks for your work on this!
Hi, thanks for the feedback and that's a good idea. I'll do a followup video on deployment.
Just use docker my man, is not hard
Dockerize and store the state in a database so the workers will still continue to work on the last remaining tasks so that when you update or deploy your django version it will store the last state and continue.
Mam, your Explanation are very well... ❤️❤️ And thank you very Much... Keep doing this type pf Deep Knowledge Videos☺️☺️
Thanks for watching and thanks for the feedback!
Thank you so much. ❣️
What could cause the worker to not succeed in executing the task, but it shows it has received?
Can we use the django models and ORM within the celery task as normal?
Of course
Thank you.
Crisply covered!
Thank you..
thank you so much!