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.