Websites generally need to serve additional files such as images, JavaScript,\nor CSS. In Django, we refer to these files as “static files”. Django provides\ndjango.contrib.staticfiles to help you manage them.
This page describes how you can serve these static files.
\nMake sure that django.contrib.staticfiles is included in your\nINSTALLED_APPS.
In your settings file, define STATIC_URL, for example:
STATIC_URL = 'static/'\nIn your templates, use the static template tag to build the URL for\nthe given relative path using the configured STATICFILES_STORAGE.
{% load static %}\n<img src="{% static 'my_app/example.jpg' %}" alt="My image">\nStore your static files in a folder called static in your app. For\nexample my_app/static/my_app/example.jpg.
Your project will probably also have static assets that aren’t tied to a\nparticular app. In addition to using a static/ directory inside your apps,\nyou can define a list of directories (STATICFILES_DIRS) in your\nsettings file where Django will also look for static files. For example:
STATICFILES_DIRS = [\n BASE_DIR / "static",\n '/var/www/static/',\n]\nSee the documentation for the STATICFILES_FINDERS setting for\ndetails on how staticfiles finds your files.
If you use django.contrib.staticfiles as explained above,\nrunserver will do this automatically when DEBUG is set\nto True. If you don’t have django.contrib.staticfiles in\nINSTALLED_APPS, you can still manually serve static files using the\ndjango.views.static.serve() view.
This is not suitable for production use! For some common deployment\nstrategies, see How to deploy static files.
\nFor example, if your STATIC_URL is defined as static/, you can\ndo this by adding the following snippet to your urls.py:
from django.conf import settings\nfrom django.conf.urls.static import static\n\nurlpatterns = [\n # ... the rest of your URLconf goes here ...\n] + static(settings.STATIC_URL, document_root=settings.STATIC_ROOT)\nDuring development, you can serve user-uploaded media files from\nMEDIA_ROOT using the django.views.static.serve() view.
This is not suitable for production use! For some common deployment\nstrategies, see How to deploy static files.
\nFor example, if your MEDIA_URL is defined as media/, you can do\nthis by adding the following snippet to your ROOT_URLCONF:
from django.conf import settings\nfrom django.conf.urls.static import static\n\nurlpatterns = [\n # ... the rest of your URLconf goes here ...\n] + static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)\nWhen running tests that use actual HTTP requests instead of the built-in\ntesting client (i.e. when using the built-in LiveServerTestCase) the static assets need to be served along\nthe rest of the content so the test environment reproduces the real one as\nfaithfully as possible, but LiveServerTestCase has only very basic static\nfile-serving functionality: It doesn’t know about the finders feature of the\nstaticfiles application and assumes the static content has already been\ncollected under STATIC_ROOT.
Because of this, staticfiles ships its own\ndjango.contrib.staticfiles.testing.StaticLiveServerTestCase, a subclass\nof the built-in one that has the ability to transparently serve all the assets\nduring execution of these tests in a way very similar to what we get at\ndevelopment time with DEBUG = True, i.e. without having to collect them\nusing collectstatic first.
django.contrib.staticfiles provides a convenience management command\nfor gathering static files in a single directory so you can serve them easily.
Set the STATIC_ROOT setting to the directory from which you’d\nlike to serve these files, for example:
STATIC_ROOT = "/var/www/example.com/static/"\nRun the collectstatic management command:
$ python manage.py collectstatic\nThis will copy all files from your static folders into the\nSTATIC_ROOT directory.
Use a web server of your choice to serve the\nfiles. How to deploy static files covers some common deployment\nstrategies for static files.
This document has covered the basics and some common usage patterns. For\ncomplete details on all the settings, commands, template tags, and other pieces\nincluded in django.contrib.staticfiles, see the staticfiles\nreference.