django-environ VS django-tailwind

This Django Starter kit takes care of automated creation of virtual environment and installing of Python packages and setting up the database with bash scripts. In addition to PostgreSQL and TailwindCSS, all the sensitive values are taken care of in a .env file using django-environ package. The virtual environment is maintained using pip-tools.

I used to do this but recently switched to using environment variables and now prefer this approach. Essentially you keep the single settings.py file that is generated with startproject, and use os.environ or os.getenv to set certain settings. Check out the FeedHQ settings.py for an example. I use direnv to automatically set my environment variables on my local machine, but django-environ is a popular alternative.

Here i decided to use django-environ's env.db() for the DATABASE_URL.

You might want to use django-environ package for this issue. Create a .env file in the project folder and follow these steps.

For this i use django-environ. Here are a few basic settings:

You could also use just django-environ package to both import config from .env and set a database url instead of using 2 dependencies. I also think of a couple things I could add to the list, maybe I should a write a blog post as well?

You can use django-environ

Docker does not do any quote parsing. For this same env file, it will set the value of the variable to `"foo"` (retaining the doublequotes in the value).

Bash, of course, requires quotes if the variable contains any special bash characters (for example, literal JSON with curly brackets), but its quote handling is much more complex. django-environ doesn't interpret bash code; it just does simple quote chomping.

There's no reliable .env syntax you can use that works in all 3 of django-environ, Docker, and bash; and any variable that should start and end with quotes that are not stripped off can't be expressed in a way that both Docker and django-environ will read in the same way.

This may seem like a nit-picking edge case, but it's indicative of the design philosophy in django-environ of trying to be "helpful", but in ways which lead to subtle confusion. The way it guesses the path to your `.env` file is another example.

[1] https://github.com/joke2k/django-environ/blob/main/environ/e...

For Django use useful environ-wrapper: django-environ

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?