Static file configuration methods in Djang

The following graphic method to give you a detailed introduction to the static file configuration method in Djang

First, django static file configuration principle
Static files are configured so that the django server can find static files to return when a user requests them.

First of all, it is important to understand a few concepts:

Media files: files uploaded by users
Static files: css, js, image, etc.
Development environment: using django built-in server to handle static files
Production environment: using apache2/nginx server to handle static file mapping
So when you configure it, you have to distinguish between the development environment and the production environment, which will be described in detail later.

Here's a quick overview of how the server looks for static files so we can configure it better.

1、
is django1.3 added an app to help developers manage static files [js, css, etc.].

Static files before django 1.3 were controlled with MEDIA_URL and MEDIA_ROOT.

in order to incorporatemedia file[Files uploaded by users] andStatic filesTo make the distinction, django 1.3 handles media files via the MEDIA_XXX configuration and static files via the STATIC_XXX configuration item.

staticfiles enables developers to assign static files to the app directory or any specified directory.

2、Difference between MEDIA_XXX and STATIC_XXX configuration items
The MEDIA_XXX configuration item is used to manage media files. Often uploaded by the FileFields field, they are stored in the directory specified by settings.MEDIA_ROOT and accessed via the path specified by settings.MEDIA_URL.

The STATIC_XXX configuration item is used to manage static files. They are assembled into the settings.STATIC_ROOT directory via the collectstatic command and accessed via the path specified by settings.STATIC_URL.

3, static file-related configuration items in detail
STATIC_ROOT configuration item

Used to specify the path where static files are stored when collectstatic is executed. In a generative environment, centralized storage of static resources facilitates the use of Lighttpd/Nginx/apache2 to host static resources. For debugging purposes, it is usually set as follows:

In django templates, you can reference the {{STATIC_URL}} variable to avoid writing the path to death. It is common to use the default setting

ADMIN_MEDIA_PREFIX must be configured as follows for static resources to be found correctly by staticfiles:

After the principle of understanding, the next introduction to the development environment and production environment in the static file specific configuration.

My django version is 1.4.21, so I'll use this version as an introduction.

One thing: the order in which the development environment staticfiles looks for static files depends on the STATIC_FINDERS configuration item, the default configuration is

1、New project lxyproject

Create a static directory under hello app for static files.

In the static directory, create a new images directory to put a picture, the same way through the url to access the

III. Production environment
As mentioned earlier, in a generation environment, centralizing static resources is beneficial to use Lighttpd/Nginx to host static resources. And the production environment usually puts the static files in the static directory under the root directory of the project.

default configuration

Here's what we're going to do.

1, configure the server, I use apache.

Installation and configuration details are available:

Ubuntu apache2 server configuration

centos7 apache httpd install and configure django project

2. Create the collectedstatic directory in the project root directory.

3. Configuration

import os

SITE_ROOT = ((__file__))
SITE_ROOT = ((SITE_ROOT, '../'))
STATIC_ROOT = (SITE_ROOT, 'collectedstatic')
STATIC_URL = '/static/'
STATICFILES_DIRS = (
 # Put strings here, like "/home/html/static" or "C:/www/django/static".
 # Always use forward slashes, even on Windows.
 # Don't forget to use absolute paths, not relative paths.
)
INSTALLED_APPS = (
 '',
 '',
 '',
 '',
 '',
 '',
 # Uncomment the next line to enable the admin:
 # '',
 # Uncomment the next line to enable admin documentation:
 # '',
 'hello',
)

 
4, run python collectstatic to collect static files of all installed APPs to the root directory collectedstatic [i.e. STATIC_ROOT].

That is, configure the

When actually releasing a django project, the management of static files may require some additional work:

Less / CoffeeScript etc. auto-compile to css/js
"Compress" css/js files to improve browser loading speeds
Consolidate fragmented css/js files to reduce browser requests
Versioning of static resource files: Browsers cache static files. When both the background code and static resource files are updated, the browser is likely to fetch outdated static resources from the cache, resulting in abnormal page display.

This is all about the static file configuration method in Djang, hope you like it.