in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your auth", "django.contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your auth", "django.contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your auth", "django.contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your auth", "django.contrib.messages.context_processors.messages", ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. 3.3. Handling HTTP requests 303 Django Documentation, Release 4.2.4.dev20230724190741

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages', ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session

in your project directory (the one that contains manage.py). Templates can live anywhere on your filesystem that Django can access. (Django runs as whatever user your server runs.) However, keeping your contrib.messages.context_processors.messages', ], }, }, ] DIRS is a list of filesystem directories to check when loading Django templates; it’s a search path. Organizing templates faster to store session data elsewhere, so Django can be configured to store session data on your filesystem or in your cache. Using database-backed sessions If you want to use a database-backed session