Repository navigation
Why did you remove the Celery and flower 3 month ago? what do you use as task queue now? thx #1237
First Check
Commit to Help
Example CodeDescriptionI am try to build a simple full stack web application to generate image. the task are long lasting so I think a task queue tool like celery + redis + flower are typical. but I found you have removed them out from your repo 3 month ago, I wonder you are using something else? Operating SystemLinux Operating System Detailsubuntu Python Version3.10.14 Additional ContextNo response |
Replies: 3 comments
|
I'd also be keen to understand this a bit more. The documentation points to this template as an example of using Celery with Fast API (https://fastapi.tiangolo.com/tutorial/background-tasks/?h=celery#caveat). I was a bit confused when I realised it wasn't here at all. I'm coming from a different language ecosystem so would be really keen to understand if it's being dropped in favour of another recommendation, or if it was just hard to maintain in the template. |
|
@tianerphil Maybe this PR can give you some more context |
|
Understood. Thank you for giving these context.
While just update you that I have add celery worker, celery beat, redis, flower into the fleet. I have to do so, Since the task meant to be very time consuming.
So far so good, It do increased the complexity of debugging, but the tools are convenient to do so, docker and flower could give the necessary debugging information in 98% cases.
Will Let you know more when I put them for pressure test.
Thx
Best Regards,
Liang ZHANG
0509119456
…---Original---
From: "Isaac ***@***.***>
Date: Thu, Jul 4, 2024 17:44 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [tiangolo/full-stack-fastapi-template] Why did you remove theCelery and flower 3 month ago? what do you use as task queue now? thx(Discussion #1237)
@tianerphil Maybe this PR can give you some more context
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I'd also be keen to understand this a bit more. The documentation points to this template as an example of using Celery with Fast API (https://fastapi.tiangolo.com/tutorial/background-tasks/?h=celery#caveat). I was a bit confused when I realised it wasn't here at all. I'm coming from a different language ecosystem so would be really keen to understand if it's being dropped in favour of another recommendation, or if it was just hard to maintain in the template.