STATIC_ROOT path mismatch in production-ready Django deployments

Answer the exact question first

When DEBUG is False, Django no longer serves static files. The collectstatic command writes them to the directory named in STATIC_ROOT. To avoid 404s, the web server must map the STATIC_URL prefix to the exact same filesystem path.

Best practices for STATIC_ROOT

• Define it relative to BASE_DIR so the value adapts when the project is moved:

  STATIC_ROOT = BASE_DIR / "staticfiles"
  

• Set STATIC_ROOT only when DEBUG is False (or use an environment variable to override in production). During development you can leave it unset or point it to a temporary folder.
• Use an environment variable to override the default in CI/CD or container images:

  STATIC_ROOT = os.getenv("DJANGO_STATIC_ROOT", BASE_DIR / "staticfiles")
  

• Ensure the directory is writable by the user that runs collectstatic.
• Run python manage.py collectstatic --noinput after the settings are resolved to verify that the directory contains the expected files.

Verifying the web‑server mapping

1. Confirm the absolute path in Django:
   

   python -c "from django.conf import settings; print(settings.STATIC_ROOT)"
   

2. Check the web‑server config:
   • NGINX – ensure an alias or root directive points to that absolute path:

     location /static/ {
         alias /full/path/to/staticfiles/;
     }
     

   • Apache – ensure a Alias directive matches:

     Alias /static/ /full/path/to/staticfiles/
     

3. From the production host run:

   curl -I http://yourdomain/static/example.css
   

   A 200 OK confirms the mapping; a 404 indicates the path is wrong.
4. Optionally, add a tiny health‑check static file (e.g., staticfiles/health.txt) and request it via browser or curl to double‑check.

Missing diagnostic detail

If you encounter a 404 after following the steps above, please provide the absolute value printed by the Django shell and the exact alias or Alias line from your web‑server configuration. That will help pinpoint any mismatch.