django-storages VS django-celery-results

I recommend using https://github.com/jschneier/django-storages for handling this

On the other side, the Django itself, together with a django-storages package, provides a wide range of file-like storage backends also using local, network, and cloud storage implementations.

the images are uploading correcty to dropbox but still have this stupid error.. same problem as here https://github.com/jschneier/django-storages/issues/1109

I have a Django application running on Heroku. To store and serve my static files, I'm using django-storages with my S3 bucket, as well as the standard Django ManifestFilesMixin. I'm also using django-pipeline.

And I hace tried https://github.com/pyutil/django-b2 https://github.com/royendgel/django-backblazeb2-storage https://github.com/jschneier/django-storages but aside from following their readme the manage.py run keeps asking me for more info and I'm really lost on what do I have to add

Doc: https://django-storages.readthedocs.io/en/latest/ Source: https://github.com/jschneier/django-storages

Django documentation suggests not hard-coding static URLs, and instead using the {% static template tag. {% static ... returns the path the browser can use to request the file. At it's simplest, that would return a path that looks up the file on your local file system. That's fine for your local dev environment but in prod we will likely use third-party libraries such as whitenoise or django-storages to improve performance of the production web server.

By far the most annoying part of this whole thing was finding some GitHub issue comment that mentioned that Lambdas automatically set the AWS_SESSION_TOKEN and AWS_SECURITY_TOKEN environment variables, and it turns out it was causing a hard-to-track-down error in the backup script's invocation of the aws client along the lines of:

If you’re unfamiliar: {% static ... returns the path the browser can use to request the file. At it's simplest, that would return a path that looks up the file on your local file system. That's fine for local dev but in prod we will likely use third-party libraries such as whitenoise or django-storages to improve performance of the production web server.

I would then suggest to use django-storages to handle uploaded files to S3 if you are not doing it already.

The Celery package provides some number of (undocumented!) result backends to store task results in different local, network, and cloud storages. The django-celery-result package adds options to use Django-specific ORM-based result storage, as well as Django-specific cache subsystem.

To keep track of task result

The field is referenced in the docs here: https://github.com/celery/django-celery-results/blob/9b7deb464b0f3fa8c063a1cc70f9fc48829f9793/docs/includes/introduction.txt, and that appears to be accurate, but I don't have any experience with d-c-r personally so I can't really help much more. Hope you figure it out!

Hello, I have been having issues with Django and sending the results of Celery workers. Celery works and produces the results and if I set the backend to the redis server, it works fine. The issue is that Django ORM is not registering the TaskResults. I have tried everything under the sun in regards to configuration and I am sure that it's not the issue. I have found this Github: https://github.com/celery/django-celery-results/issues/102