Thank you very much for this video, I was able to get celery beat working in my app by following it. You do a great job, appreciate the content you are poutting out 👏👏
Why do background tasks require an endpoint (urls.py)? Surely those can then be triggered by public users (if they guess the endpoint correctly )? I would have thought that background tasks simply live withing tasks.py and are triggered my the application without exposing an endpoint ... ?
I think he’s just demonstrating that if you were building an application where you’d like users to be able to dynamically create/modify tasks that they could from your app frontend by making a call to an endpoint (think like IT admin dashboard type apps where allowing the user to schedule some kind of scan is pretty common) Otherwise, yea if you’re just wanting to setup tasks that you want the app to process in the background without anyone ever touching then just create the schedule in the admin panel that invokes your premade task and you’re good to go.
Thank you very much for this video, I was able to get celery beat working in my app by following it. You do a great job, appreciate the content you are poutting out 👏👏
Thank you so much. What's your favorite between Flask and Django ? It's very hard for me to choose one when i want to start a new project 😅
Hey, im new to celery beat, do you have recent tutor on this topic, i mean, i need to start from scratch
.
Thank you. you are the BEST!
How do i set up the timezone?
I do not want celery to get UTC time.
Thanks for any comments/advices
please if you can make video on how to deploy celery on vps
at this time I can't pay for the coaching
I thin this is what i wanted
wierd my task wont start, however if scheduled (beats) it runs like a charm
thank you
The imports from the model is not working it's throwing the errors as there's is nothing called these tables
Why do background tasks require an endpoint (urls.py)? Surely those can then be triggered by public users (if they guess the endpoint correctly
)? I would have thought that background tasks simply live withing tasks.py and are triggered my the application without exposing an endpoint ... ?
I think he’s just demonstrating that if you were building an application where you’d like users to be able to dynamically create/modify tasks that they could from your app frontend by making a call to an endpoint (think like IT admin dashboard type apps where allowing the user to schedule some kind of scan is pretty common) Otherwise, yea if you’re just wanting to setup tasks that you want the app to process in the background without anyone ever touching then just create the schedule in the admin panel that invokes your premade task and you’re good to go.