django-db-queue
rapidpro
django-db-queue | rapidpro | |
---|---|---|
5 | 1 | |
158 | 37 | |
0.0% | - | |
6.3 | 0.0 | |
4 days ago | 4 days ago | |
Python | Python | |
BSD 2-clause "Simplified" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django-db-queue
- Django Styleguide
-
Show HN: Chard – simple async/await background tasks for 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!
-
Simple Task Queue system that works with Django 4 / Python 3.9?
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.
-
Dealing with tasks that take longer than 30 seconds on Heroku
Check out https://github.com/dabapps/django-db-queue for example.
-
what are 3 django packages everyone should know about?
django-db-queue: queue without needing redis, celery, etc.
rapidpro
-
Django Styleguide
Maybe you need to turn this into an article because over the last decade of working with Django, we've learnt the same lessons, sometimes the hard way. Learning to never import real models into data migrations was a big one.
I recently wanted to move a model between apps and ended up going the route of create new table, copy all rows over, delete old table. It was annoying, but the only way to make it work with regular migrations.
We ended up writing our own script[1] to squash migrations, and I'd love to know if there's a better way. We needed something that works for clean installs or existing installs that already have the current migrations installed - so it generates empty migrations which get applied on existing installs, and then they get replaced with real initial migrations on clean installs starting from a new release.
1. https://github.com/nyaruka/rapidpro/blob/main/tools/squash_m...
What are some alternatives?
django-q - A multiprocessing distributed task queue for Django
spinach - Modern Redis task queue for Python 3
django-fsm - Django friendly finite state machine support
django-readers - A lightweight function-oriented toolkit for better organisation of business logic and efficient selection and projection of data in Django projects.
django-constance - Dynamic Django settings.
django-api-domains - A pragmatic styleguide for Django API Projects
dramatiq - A fast and reliable background task processing library for Python 3.
django-elasticsearch-dsl - This is a package that allows indexing of django models in elasticsearch with elasticsearch-dsl-py.
Sentry - Developer-first error tracking and performance monitoring
django-rest-framework - Web APIs for Django. 🎸
Django-Styleguide - Django styleguide used in HackSoft projects