How does collectstatic work and how should static files be served in production? collectstatic कैसे काम करता है और प्रोडक्शन में स्टैटिक फाइलों को कैसे सर्व करना चाहिए?

During development, Django's runserver automatically serves static files (CSS, JS, images) from each app's static/ directory, but this behavior is disabled when DEBUG=False since Django itself is not meant to serve static assets efficiently in production. manage.py collectstatic walks every app's static directory and copies all files into a single location defined by STATIC_ROOT.

That consolidated directory is then served directly by Nginx (or another web server) bypassing the Django/Gunicorn application process entirely, which is far faster since a dedicated web server is optimized for serving files. A common alternative is WhiteNoise, a middleware that lets Gunicorn serve compressed, cache-friendly static files directly without needing a separate Nginx static-file configuration.

STATIC_URL = '/static/'
STATIC_ROOT = BASE_DIR / 'staticfiles'
python manage.py collectstatic --noinput