Development: STATIC_ROOT is useless during development, it’s only required for deployment. While in development, STATIC_ROOT does nothing. You even don’t need to set it. Django looks for static files inside each app’s directory (myProject/appName/static) and serves them automatically. This is the magic done by manage.py runserver when DEBUG=True. Deployment

Development

STATIC_ROOT is useless during development, it’s only required for deployment. While in development, STATIC_ROOT does nothing. You even don’t need to set it. Django looks for static files inside each app’s directory (myProject/appName/static) and serves them automatically. This is the magic done by manage.py runserver when DEBUG=True.

Deployment

When your project goes live, things differ. Most likely you will serve dynamic content using Django and static files will be served by Nginx. Why? Because Nginx is incredibly efficient and will reduce the workload off Django. This is where STATIC_ROOT becomes handy, as Nginx doesn’t know anything about your django project and doesn’t know where to find static files. So you set STATIC_ROOT = '/some/folder/' and tell Nginx to look for static files in /some/folder/. Then you run manage.py collectstatic and Django will copy static files from all the apps you have to /some/folder/. Extra directories for static files: STATICFILES_DIRS is used to include additional directories for collectstatic to look for. For example, by default, Django doesn’t recognize /myProject/static/. So you can include it yourself.

STATIC_URL = '/static/'

if not DEBUG: 
    STATIC_ROOT = '/home/django/www-data/site.com/static/'

STATICFILES_DIRS = [
    os.path.join(BASE_DIR, 'static/'),
]
 MEDIA_ROOT is the folder where files uploaded using FileField will go. STATIC_ROOT is the folder where static files will be stored after using manage.py collectstatic

STATICFILES_DIRS is the list of folders where Django will search for additional static files aside from the static folder of each app installed.