django-fsm
django-db-queue
django-fsm | django-db-queue | |
---|---|---|
3 | 5 | |
2,315 | 158 | |
- | 0.0% | |
4.1 | 6.3 | |
25 days ago | 3 days ago | |
Python | Python | |
MIT License | BSD 2-clause "Simplified" License |
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-fsm
-
How to separate tables based on the model using FSM and FSM-Log?
I'm currently logging status changes to several models in my Django REST API using the django-fsm and django-fsm-log packages. However, all of the logs are stored in a single table. This is gonna end up being a massive table that will take time to run through to do analysis and reporting. To make it easier I'd like to either break out the logging table by each individual model or sort them by the highest level model that's associated. I'll explain what I mean.
-
Checking and changing status of model objects
...see https://github.com/viewflow/django-fsm
-
what are 3 django packages everyone should know about?
django-fsm - State management and transitions.
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.
What are some alternatives?
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
django-q - A multiprocessing distributed task queue for Django
django-guardian - Per object permissions for Django
django-constance - Dynamic Django settings.
django-webpack-loader - Transparently use webpack with django
spinach - Modern Redis task queue for Python 3
django-jazzmin - Jazzy theme for Django
django-elasticsearch-dsl - This is a package that allows indexing of django models in elasticsearch with elasticsearch-dsl-py.
django-rest-framework - Web APIs for Django. 🎸
django-post_office - A Django app that allows you to send email asynchronously in Django. Supports HTML email, database backed templates and logging.