collectstatic for production in Django

Introduction

The collectstatic command gathers all static files from your Django apps into one place. This makes it easy to serve them efficiently in production.

When you want to prepare your static files (CSS, JavaScript, images) for deployment.

Before deploying your Django project to a live server.

When you add or update static files and want to make sure the server uses the latest versions.

To organize static files from multiple apps into a single folder for easy serving.

When using a web server like Nginx or Apache to serve static files separately from Django.

Syntax

Django

python manage.py collectstatic

This command copies static files into the directory set by STATIC_ROOT in your settings.

You usually run this command once before deploying your site.

Examples

Runs the command and asks for confirmation before copying files.

Django

python manage.py collectstatic

Runs the command without asking for confirmation, useful for automated deployments.

Django

python manage.py collectstatic --noinput

Clears the target directory before collecting static files.

Django

python manage.py collectstatic --clear

Sample Program

This example shows the minimal settings needed and the command to collect static files. After running, all static files from apps and STATICFILES_DIRS are copied to staticfiles folder.

Django

# settings.py
STATIC_URL = '/static/'
STATIC_ROOT = BASE_DIR / 'staticfiles'

# Terminal command
python manage.py collectstatic

# Output example
# You will see lines like:
# 127 static files copied to '/path/to/project/staticfiles'

Important Notes

Make sure STATIC_ROOT is set and points to a folder outside your app directories.

Do not serve static files with Django in production; use a web server instead.

Run collectstatic every time you change static files before deploying.

Summary

collectstatic gathers all static files into one folder for easy serving.

Run it before deploying your Django project to production.

Set STATIC_ROOT in settings to tell Django where to collect files.

Practice

1. What is the main purpose of running collectstatic in a Django project before deployment?

easy

A. To gather all static files into one folder for easy serving in production

B. To compile Python code into bytecode

C. To migrate database changes

D. To start the Django development server

Solution

1. Step 1: Understand what collectstatic does

   The collectstatic command collects all static files from apps and places them into a single directory.

2. Step 2: Recognize its role in production

   This makes it easier for the web server to serve static files efficiently in production environments.

3. Final Answer:

   To gather all static files into one folder for easy serving in production -> Option A

4. Quick Check:

   collectstatic gathers static files [OK]

Hint: Remember: collectstatic collects static files for production [OK]

Common Mistakes:

• Confusing collectstatic with database migrations
• Thinking collectstatic runs the server
• Assuming collectstatic compiles Python code

2. Which setting must be defined in settings.py to specify where collectstatic will gather static files?

easy

A. STATIC_ROOT

B. MEDIA_ROOT

C. STATIC_URL

D. STATICFILES_DIRS

Solution

1. Step 1: Identify the setting for static file collection

   STATIC_ROOT tells Django the directory where collected static files will be placed.

2. Step 2: Differentiate from other static settings

   STATIC_URL is the URL prefix, MEDIA_ROOT is for user-uploaded files, and STATICFILES_DIRS lists additional static file locations.

3. Final Answer:

   STATIC_ROOT -> Option A

4. Quick Check:

   STATIC_ROOT sets collection folder [OK]

Hint: STATIC_ROOT is the folder for collected static files [OK]

Common Mistakes:

• Confusing STATIC_ROOT with STATIC_URL
• Using MEDIA_ROOT for static files
• Thinking STATICFILES_DIRS is the collection folder

3. Given the following settings.py snippet:

STATIC_URL = '/static/'
STATIC_ROOT = '/var/www/example.com/static/'
STATICFILES_DIRS = ['/home/user/project/assets']

What happens when you run python manage.py collectstatic?

medium

A. Static files are deleted from /var/www/example.com/static/

B. Static files remain in /home/user/project/assets and are not copied

C. Static files from assets and app static folders are copied to /var/www/example.com/static/

D. An error occurs because STATIC_URL is not a valid path

Solution

1. Step 1: Understand the role of STATICFILES_DIRS and STATIC_ROOT

   STATICFILES_DIRS lists extra folders with static files, and STATIC_ROOT is the destination for collected files.

2. Step 2: What collectstatic does

   Running collectstatic copies all static files from app static folders and STATICFILES_DIRS into STATIC_ROOT.

3. Final Answer:

   Static files from assets and app static folders are copied to /var/www/example.com/static/ -> Option C

4. Quick Check:

   collectstatic copies files to STATIC_ROOT [OK]

Hint: collectstatic copies all static files to STATIC_ROOT [OK]

Common Mistakes:

• Thinking STATIC_URL affects file copying
• Believing files stay in source folders
• Assuming collectstatic deletes files

4. You run python manage.py collectstatic but get an error: Permission denied for the STATIC_ROOT directory. What is the best way to fix this?

medium

A. Remove the STATIC_ROOT setting from settings.py

B. Change permissions of the STATIC_ROOT folder to allow write access

C. Run collectstatic without any arguments

D. Delete all static files from your apps

Solution

1. Step 1: Understand the error cause

   The Permission denied error means Django cannot write files to the STATIC_ROOT folder due to OS permissions.

2. Step 2: Fix permissions

   Changing the folder permissions to allow write access for the user running the command resolves this issue.

3. Final Answer:

   Change permissions of the STATIC_ROOT folder to allow write access -> Option B

4. Quick Check:

   Fix permissions to allow writing [OK]

Hint: Fix folder permissions to allow writing [OK]

Common Mistakes:

• Removing STATIC_ROOT disables static collection
• Running collectstatic without fixing permissions
• Deleting static files unnecessarily

5. You want to deploy your Django project to production. Your settings.py has:

STATIC_URL = '/static/'
STATIC_ROOT = '/var/www/example.com/static/'
STATICFILES_DIRS = ['/home/user/project/assets']

After running collectstatic, you notice some static files are missing from /var/www/example.com/static/. What could be a reason and how to fix it?

hard

A. Static files are not copied if DEBUG is True; set DEBUG to False

B. You forgot to set STATIC_URL to the correct path

C. You need to run python manage.py migrate before collectstatic

D. Some static files are inside app folders but not declared in STATICFILES_DIRS; add app static folders or check AppConfig

Solution

1. Step 1: Understand where static files come from

   Django collects static files from app static folders and STATICFILES_DIRS. If files are missing, they might be in app folders not properly recognized.

2. Step 2: Fix by ensuring app static folders are included

   Check that apps have static folders and are correctly configured. Adding missing folders to STATICFILES_DIRS or verifying app configs helps.

3. Final Answer:

   Some static files are inside app folders but not declared in STATICFILES_DIRS; add app static folders or check AppConfig -> Option D

4. Quick Check:

   Missing files often mean missing source folders [OK]

Hint: Check all static source folders are included [OK]

Common Mistakes:

• Thinking STATIC_URL affects file copying
• Running migrate instead of collectstatic
• Assuming DEBUG controls static file copying