django-rq VS cookiecutter-django

For simple stuff, I tend to use https://github.com/rq/django-rq. Although scheduling tasks there does not work well in my experience. If I need something to run by schedule, than better just plain cron.

Performing tests on student images can be a time-consuming process, taking several minutes. Application has to download the image from the registry, create a container, wait for the application to load, and perform the test scenarios. To efficiently utilize the available hardware and handle increased server demand during peak times, a task queue was implemented using django-rq.

Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq

I use RQ (Redis Queue) and it's very cool! https://github.com/rq/django-rq https://python-rq.org/patterns/django/

I love the simplicity of this idea because for lots of sites the database works just fine as a queue backend and it reduces the amount of infrastructure needed. I currently use https://github.com/dabapps/django-db-queue for devmarks.io which also uses the database to store tasks instead of a dedicated queue infrastructure. `Django Q` also has an option to use the database, but I haven't tested it at all: https://django-q.readthedocs.io/en/latest/configure.html#orm. And if you are already running `redis` for your site, https://github.com/rq/django-rq is another option.

The one benefit of this package is that it is async-first which will be beneficial as Django continually adds in more async capabilities. Nice work! I'm looking forward to trying this out and seeing how it works!

https://github.com/rq/django-rq if you already have redis available or https://github.com/dabapps/django-db-queue for something even simpler. I’ve used both and vastly prefer them over celery.

if you use redis there is https://github.com/rq/django-rq as well

cookiecutter https://github.com/pydanny/cookiecutter-django

"1" is definitely something I'd like the team to focus on. Cookie-cutter django aims at it (https://github.com/pydanny/cookiecutter-django) but IDK I think it goes a little too far, and we should have better out-of-the-box options. I think we have this situation because of the unwillingness to make backward incompatible changes.

Use Django Environ for secret keys etc, have a look at 12 factor https://12factor.net and https://github.com/pydanny/cookiecutter-django for a solid example of a best practise setup.

Have you seen https://github.com/pydanny/cookiecutter-django ?

I don't have production level examples but cookie cutter django covers setting up points 3,4,6 https://github.com/pydanny/cookiecutter-django for you. django-allauth for point 6

You really should take a look at cookiecutter it makes bootstrapping projects easier and more customizable. You can also peek at cookiecutter Django.