collectstatic for production in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run python manage.py collectstatic in Django?

In a Django project, you run python manage.py collectstatic. What is the main effect of this command?

A It copies all static files from each app and places them into the directory specified by <code>STATIC_ROOT</code>.

B It deletes all static files from the project to free up space.

C It compiles Python code into bytecode for faster execution.

D It runs the development server to serve static files automatically.

💡 Hint

Think about where static files need to be collected for production deployment.

The collectstatic command gathers all static files from your apps and places them in the STATIC_ROOT folder. This folder is then used by the web server to serve static content in production.

📝 Syntax

intermediate

Which setting must be set correctly for collectstatic to work?

To use collectstatic properly, which Django setting must point to an absolute directory path where static files will be collected?

A MEDIA_ROOT

B STATIC_URL

C STATIC_ROOT

D TEMPLATES_DIR

💡 Hint

This setting defines the folder where static files are gathered for production.

STATIC_ROOT is the absolute path where collectstatic copies all static files. STATIC_URL is the URL prefix to access static files, not a file path.

❓ state_output

advanced

What is the output of collectstatic if STATIC_ROOT is not set?

You run python manage.py collectstatic but forgot to set STATIC_ROOT in your settings. What will happen?

A It raises an error saying <code>You're using the staticfiles app without having set the STATIC_ROOT setting to a filesystem path.</code>

B It runs successfully but does not copy any files.

C It collects static files into the default <code>staticfiles</code> folder automatically.

D It ignores static files and only collects media files.

💡 Hint

Think about what Django requires to know where to put collected files.

If STATIC_ROOT is not set, Django cannot know where to collect static files and raises a clear error message.

🔧 Debug

advanced

Why are static files not updating after running collectstatic?

You updated some CSS files in your app and ran python manage.py collectstatic. However, the changes are not visible in production. What is a likely cause?

A You forgot to restart the Django development server.

B The web server is caching old static files; browser or server cache needs clearing.

C The <code>STATIC_URL</code> setting is missing in <code>settings.py</code>.

D You need to run <code>python manage.py migrate</code> to update static files.

💡 Hint

Static files are often cached by browsers or servers to improve speed.

After running collectstatic, old static files may still be cached by the browser or web server. Clearing caches or using versioned filenames helps.

🧠 Conceptual

expert

Why is collectstatic important for production but not for development?

Explain why Django projects require running collectstatic before deploying to production, but not during development.

A In development, static files are compiled on the fly; in production, they are converted to Python bytecode.

B In development, static files are ignored; in production, they are embedded inside HTML templates.

C In development, static files are stored in the database; in production, they must be collected into the file system.

D In development, Django serves static files automatically; in production, static files must be collected and served by a web server for efficiency and security.

💡 Hint

Think about how Django handles static files differently in development vs production environments.

Django's development server automatically serves static files for convenience. In production, a dedicated web server serves static files for better performance and security, so collectstatic gathers them in one place.

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