django-tailwind VS django-debug-toolbar

Most of our installation is done but we haven't configured Tailwind yet. django-tailwind is already installed with the required Python packages but we'll need to compile this to fully setup Tailwind and make it ready to work in our local development environment.

I'm currently using Django + TailwindCSS to build small apps, sometimes relying on JS or even with some other Django app to handle dynamic behavior on the front-end (e.g. django-formset for improving forms). I've been achieving very interesting results with this stack so far.

I like the way that django-tailwind handles it. Still requires npm locally, but puts some nice management command wrappers around it.

There are many ways to set up Tailwind CSS in Django. One way to do so is by using a package called django-tailwind. This package provides an easy way to use Tailwind CSS in a Django project.

Hi, Thanks for taking the time to reply. I've had several issues with trying to integrate it; the key problem I'm having at the moment is running manage.py tailwind commands in my dockerfile. The example dockerfile requires these commands to be run, but for some reason I am constantly getting a manage.py cannot be found error. I have checked my directories, and it seems to be in the right place, but I cannot seem to resolve this error at the moment.

django-tailwind improved my experience with this stack markedly.

Technically, you can use any CSS framework, including Tailwind, for Django. Most of the time, dropping that CDN into your template will be enough (i.e. bootstrap 5 or bulma) to get started.

Are you using the django-tailwind package?

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