Summernote VS django-storages

Summernote

We use Summernote which is fine, there can be bugs with our integration but that is more down to our hacking around with it than the actual software.

TypeError: e.attr(...).tooltip is not a function(…) · Issue #2157 · summernote/summernote

These past days I tried Action Text for the first time and got a bit disappointed with it, in the end I ended up using Summernote (https://summernote.org/) instead, here are my thoughts on what could be improved:

You can fairly easily add the ability to edit the text using something like https://summernote.org/ This one is for bootstrap, but there are others that are pretty good. (there's another one I've used before but I can't think of the name... thought it started with an "L".)

I still need to add some dolls, but add the events list, the event details are incomplete but it is easy to edit although the data is saved in a database (mongodb) it is created with https://summernote.org, which works like word, but transforms the content to html.

WYSIWYG Editor https://summernote.org

See: https://summernote.org/

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.