django-debug-toolbar VS django-guardian

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/.

You can mitigate the pain by using libraries like accesscontrol, express-rbac, django-guardian, etc., to manage authorization more declaratively. But making sure nothing leaks is still a significant challenge.

These pieces fit together very well and are sufficient for replacing most of the goodies Django provides. However, there's one piece missing. Django has a built-in permissions feature, but it's limited to model-level control, i.e., if a user or group has X access to model type Y. Many users have been using the popular django-guardian package to implement row-level permissions. It allows you to establish permissions between users/groups and objects, manages the underlying permission database tables, and provides APIs for configuring and checking such permissions.

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

Could use django-guardian for this instead: https://github.com/django-guardian/django-guardian

I was about to use django-guardian until I came across the following in the official documentation:

django-guardian for per object permissions