django_dx
rq
django_dx | rq | |
---|---|---|
3 | 27 | |
31 | 9,540 | |
- | 1.0% | |
0.0 | 8.6 | |
about 1 year ago | 8 days ago | |
Python | Python | |
- | 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_dx
-
What libraries do you use the most alongside django?
Pyenv, poetry, pylint, gunicorn, celery, etc. Everything is right there https://github.com/betaflag/django_dx
-
Tricks for starting a new project
My trick is to place all my tricks in a GitHub repo that I can simply fork or copy π from https://github.com/betaflag/django_dx
-
Suggest some open-source Django projects to get inspiration from regarding best practices, testing, files structure, coding style
https://github.com/betaflag/django_dx is how I setup my Django projects
rq
-
Redis Re-Implemented with SQLite
That's pretty cool. Reckon it would work with existing code that calls Redis over the wire for RQ?
https://python-rq.org
-
The Many Problems with Celery
https://github.com/rq/rq is to the rescue.
-
Keep the Monolith, but Split the Workloads
We use RQ[0], it has Redis as a dependency. Itβs pretty straightforward and weβre very happy with it. If you are using Django you may want to look at Django RQ[1] as well. RQ has built in scheduling capabilities these days, but historically it did not so we used (and still use) RQ Scheduler[2] which I think still has some advantages over the built in stuff.
[0] https://python-rq.org/
-
SQL Maxis: Why We Ditched RabbitMQ and Replaced It with a Postgres Queue
Also had a similar experience using RabbitMQ with Django+Celery. Extremely complicated and workers/queues would just stop for no reason.
Moved to Python-RQ [1] + Redis and been rock solid for years now.
[1] https://python-rq.org/
- Ask HN: Redis Queue Hacks and Questions
- What libraries do you use the most alongside django?
-
Recommendations other than celery to send an API processing in background, which would only take 5 mins to process and API usage would be once a month or so.
Yep, rq is simple and good: https://python-rq.org/ It also has a Django wrapper: https://github.com/rq/django-rq
-
GPU instance crashes when two python processes use the same pt file
We have a GPU (G5) instance that uses Python RQ (https://python-rq.org/).
- Dynamically update periodic tasks in Celery and Django
- Celery + RabbitMQ alternatives
What are some alternatives?
telegram-bot-template - π€ Template for telegram bot using postgres, pgbouncer, redis, docker, amplitude, prometheus, grafana, CI
celery - Distributed Task Queue (development branch)
docker-compose-actions-workflow - GitHub Actions workflow example using Docker Compose to build and test a multi-container stack
huey - a little task queue for python
FeedHQ - FeedHQ is a web-based feed reader
RabbitMQ - Open source RabbitMQ: core server and tier 1 (built-in) plugins
MyFridge - π An application that facilitates everyday life by analyzing the user's available products and returning a list of dishes that can be prepared from the given ingredients.
mrq - Mr. Queue - A distributed worker task queue in Python using Redis & gevent
zimagi - Zimagi - Modular Data Integration, Distributed Processing, and API Publishing Platform
procrastinate - PostgreSQL-based Task Queue for Python
django_slack - This is a sample application I made for teaching how to integrate Slack with Django.
Apache Kafka - Mirror of Apache Kafka