5 ms·
Yeah, that was my issue. Seemed like a ridiculous amount of stuff just to process a few jobs once a day in the background. Eventually I found django-background-
by soperj 7y ago
Yeah, that was my issue. Seemed like a ridiculous amount of stuff just to process a few jobs once a day in the background. Eventually I found django-background-tasks and have bene using that ever since. It uses whatever database you're already using, so very quick and easy.
- wojcikstefan 7y agoAt a glance, https://github.com/lilspikey/django-background-task https://github.com/lilspikey/django-background-task indeed seems like a good and easy way to get started. You can later switch to something more specialized once you hit the right scale or when you need more sophisticated features.
- slig 7y agoJust FYI, this fork is updated https://github.com/arteria/django-background-tasks https://github.com/arteria/django-background-tasks
- andybak 7y agoYep. That's the solution I've been recommending over Celery for most people. Half the time people seem to reach for Celery etc all they want to do is run a long task without blocking the response. That's a helleva lot of code to add to your project to just have that functionality.