django-debug-toolbar VS django-compressor

The reason behind this splitting is that we can safely use packages and related settings only where we need. For example, this starter kit has the package django-debug-toolbar. This is only intended for your development environment and not for your production. This can be very risky if used in production because if your Django project encounters errors, all the debug info will be shown to the user which is a severe security risk. Similarly, for tracking errors in production, we're using Sentry which is not needed in our local environment since we already have django-debug-toolbar. For keeping these settings file separate so that they don't conflict with each other, the settings file is split for serving different environments.

django-debug-toolbar: https://github.com/jazzband/django-debug-toolbar

https://github.com/jazzband/django-debug-toolbar/issues?q=is%3Aopen+is%3Aissue+label%3ABug

https://github.com/jazzband/django-debug-toolbar Allows you to check which sql queries are being run on your app. See if they are optimized first.

Perhaps try the django-debug-toolbar. It might be able to tell you what is causing the slow load time.

I would start with https://github.com/jazzband/django-debug-toolbar and figure out what causes the slowness.

-> The debugging above from django-debug-toolbar

Documentation, including installation and configuration instructions, is available at https://django-debug-toolbar.readthedocs.io/.

In general, you can use almost any plain JS library by simply loading it in your view template. For forms specifically, you can write custom widgets and define dependencies to libraries via form assets. django-compressor might be worth a look if you go heavy on this.

Idk, it depends on how much you care about the page loading time. Even without the PurgeCSS filter, I would recommend the Django Compressor app. I use it on all my websites. It automatically merges your css/js files and minifies them (removes white spaces, comments, etc.). It also creates a unique name for the combined CSS so if you changed your CSS files, your users will always see the fresh version, not the cached by the browser one.

django_compressor - for merging and minimizing css and js assets

django-compressor with django-libsass for auto sass compilation

But isn't that what you have django-compressor for?

The external dependencies were downloaded into the static/ folder containing all frontend assets using yarn and a package.json. Other than that, yarn was not used. Next I ran a bash script that removed all files I did not need, keeping the javascript, css and font files that should be served. In html, these files where directly included. I knew that loading many files is bad, so I used django-compressor to combine them into one big file. Conveniently, this tool also provided me with a way to compile scss.