whitenoise
django-q
whitenoise | django-q | |
---|---|---|
8 | 8 | |
2,438 | 1,791 | |
- | - | |
8.4 | 0.0 | |
3 days ago | about 2 months ago | |
Python | Python | |
MIT License | MIT 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.
whitenoise
-
How to load static files while deploying using nginx
You can use whitenoise. https://github.com/evansd/whitenoise
-
Deploy a REST API using Serverless, Django and Python
We’ll use this library to serve our static admin files. I’m not going to go over all the configuration details here, but you can feel free follow them on your own. Make sure the static files are part of the Lambda package.
-
'collectstatic' command fails when WhiteNoise is enabled
I'm trying to serve static files through WhiteNoise as per Heroku's recommendation. When I run collectstatic in my development environment, this happens:
-
what are 3 django packages everyone should know about?
Waitress - for serving your application easily (pairs very well with Whitenoise).
-
How to Scale Django
3) Caching static assets - both of static assets. So maybe try deploying a Django app in a production environment and cache the static assets. You could put them behind a service like Cloudflare which will take care of that for you, or have a look at something like [Whitenoise](https://github.com/evansd/whitenoise) which will add the correct HTTP headers for you. You can spend some time reading about HTTP Caching headers and even try writing a simple middleware which caches certain requests to your Django app (just for learning purposes).
-
Serving Static files from AWS S3 Issue
FWIW, I always use Whitenoise to serve Static files when I use Heroku, and only keep Media files on AWS. It works well.
-
Deployment Django on Heroku With a Different Branch
In the beginning of the project, I chose Google Cloud Platform as the "Cloud Provider". But for simplicity and easy to use I switched to WhiteNoise to serve staticfiles.
django-q
-
Background jobs with Django
Other options are DjangoQ and Huey, which tend to work ok. Of the two I prefer DjangoQ. Database backed, don't require the Redis/Celery rigmarole.
-
Why are Notifications so much work to do in Django?
If you want a "simple" solution for sending email, the simplest that will likely last you the longest is using DjangoQ to create a background task that looks for model records that have not been emailed. Then use Sendgrid with an email backend to send them. You can use a library that already provides a Sendgrid email backend as well.
- Simple Task Queue system that works with Django 4 / Python 3.9?
-
celery and call_command
Take a look at Django-Q I was using it before moving to celery. Seems great just wanted experience with celery. Much simpler to get setup. Even use Django admin to schedule your tasks. Other option is a management command thats called using the full path of the python virtual env from a cron entry.
-
New DigitalOcean Pricing
App Platform is a great concept, but we hit a dealbreaking road block when trying to migrate some Python apps with job queues. Their runtime (gVisor) doesn't support semaphore locks, which is used by Pythons multiprocessing and in turn used by most job runners (we discovered it with django-q, but I think most, if not all of them including Celery, rely on this, see link below).
The build times for Dockerfiles are also atricious… our build failed after 40 minutes by running out of memory and the multi-stage Dockerfile really wasn't anything special. We would have just used the images hosted on Github Container Registry, but App Platform only supports a limited range of Docker registries too. Note: the images build in 3 minutes on Github Actions.
As far as I can see it is also not possible to add any block storage too. While I mostly work on projects that use object storage anyway, SOME things just need persistent block storage. Which is annoying, since DigitalOcean HAS block storage… just not for App Platform.
I really wanted to use it, but man they make it hard.
https://github.com/Koed00/django-q/issues/522#issuecomment-1...
-
Database backed task queue recommendations?
I use Django Q with ORM broker. Store tasks in db and retry if failed. You can also view/manage your queue in Django admin if you use ORM as broker (https://django-q.readthedocs.io/en/latest/brokers.html#django-orm).
-
what are 3 django packages everyone should know about?
django-q - Light weight task queue. When celery is too much over head.
-
Whats the best Task Queue/Scheduler that could run my API calls in the background?
Check out https://github.com/Koed00/django-q
What are some alternatives?
django-webpack-loader - Transparently use webpack with django
django-db-queue - Simple database-backed job queue
django-components - Create simple reusable template components in Django.
django-jazzmin - Jazzy theme for Django
Wagtail - A Django content management system focused on flexibility and user experience
django-rq - A simple app that provides django integration for RQ (Redis Queue)
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
django-post_office - A Django app that allows you to send email asynchronously in Django. Supports HTML email, database backed templates and logging.
dramatiq - A fast and reliable background task processing library for Python 3.
django-compressor - Compresses linked and inline javascript or CSS into a single cached file.
django-health-check - a pluggable app that runs a full check on the deployment, using a number of plugins to check e.g. database, queue server, celery processes, etc.