Here's a list of settings available in Django core and their default values.\nSettings provided by contrib apps are listed below, followed by a topical index\nof the core settings. For introductory material, see the settings topic\nguide.
\nABSOLUTE_URL_OVERRIDESLink to this heading#Awalan: {} (Kamus kosong)
A dictionary mapping "app_label.model_name" strings to functions that take\na model object and return its URL. This is a way of inserting or overriding\nget_absolute_url() methods on a per-installation basis. Example:
ABSOLUTE_URL_OVERRIDES = {\n 'blogs.blog': lambda o: "/blogs/%s/" % o.slug,\n 'news.story': lambda o: "/stories/%s/%s/" % (o.pub_year, o.slug),\n}\nThe model name used in this setting should be all lowercase, regardless of the\ncase of the actual model class name.
\nADMINSLink to this heading#Awalan: {} (Daftar kosong)
A list of all the people who get code error notifications. When\nDEBUG=False and AdminEmailHandler\nis configured in LOGGING (done by default), Django emails these\npeople the details of exceptions raised in the request/response cycle.
Setiap barang dalam daftar harus berupa tuple dari (Nama lengkap, alamat surel). Contoh:
\n[('John', 'john@example.com'), ('Mary', 'mary@example.com')]\nALLOWED_HOSTSLink to this heading#Awalan: {} (Daftar kosong)
A list of strings representing the host/domain names that this Django site can\nserve. This is a security measure to prevent HTTP Host header attacks, which are possible even under many\nseemingly-safe web server configurations.
\nNilai-nilai dalam daftar ini dapat berupa sepenuhnya nama-nama berkualitas (misalnya 'www.example.com'), dalam kasus mereka akan cocok terhadap kepala Host permintaan tepatnya (kurang-peka-kasus, tidak termasuk port). Sebuah nilai dimulai dengan titik dapat digunakan sebagai wildcard subranah: '.example.com' akan cocok example.com, www.example.com, dan subranah lainnya dari example.com. Nilai dari '*' akan cocok apapun; dalam kasus ini anda bertanggung jawab untuk menyediakan pengesahan anda sendiri dari kepala Host (mungkin dalam sebuah middleware; jika demikian middleware ini harus didaftarkan dahulu dalam MIDDLEWARE).
Django also allows the fully qualified domain name (FQDN) of any entries.\nSome browsers include a trailing dot in the Host header which Django\nstrips when performing host validation.
Jika kepala Host (atau X-Forwarded-Host jika USE_X_FORWARDED_HOST diadakan) tidak cocok nilai apapun dalam daftar ini, metode django.http.HttpRequest.get_host() akan memunculkan SuspiciousOperation.
When DEBUG is True and ALLOWED_HOSTS is empty, the host\nis validated against ['.localhost', '127.0.0.1', '[::1]'].
ALLOWED_HOSTS adalah juga checked when running tests.
This validation only applies via get_host();\nif your code accesses the Host header directly from request.META you\nare bypassing this security protection.
APPEND_SLASHLink to this heading#Awal: True
Ketika disetel menjadi True, jika URL diminta tidak cocok salah satu dari pola dalam URLconf dan itu tidak berakhir dalam sebuah garis miring, sebuah pengalihan HTTP diterbitkan ke URL sama dengan sebuah garis miring ditambahkan. Catat bahwa pengalihan mungkin menyebabkan data apapun diajukan dalam sebuah permintaan POST menjadi hilang.
Pengaturan APPEND_SLASH hanya digunakan jika CommonMiddleware dipasang (lihat Middleware). Lihat juga PREPEND_WWW.
CACHESLink to this heading#Awal:
\n{\n 'default': {\n 'BACKEND': 'django.core.cache.backends.locmem.LocMemCache',\n }\n}\nA dictionary containing the settings for all caches to be used with\nDjango. It is a nested dictionary whose contents maps cache aliases\nto a dictionary containing the options for an individual cache.
\nThe CACHES setting must configure a default cache;\nany number of additional caches may also be specified. If you\nare using a cache backend other than the local memory cache, or\nyou need to define multiple caches, other options will be required.\nThe following cache options are available.
BACKENDLink to this heading#Awalan: '' (String kosong)
Backend cache untuk digunakan. Backend cache siap-pakai adalah:
\n'django.core.cache.backends.db.DatabaseCache'
'django.core.cache.backends.dummy.DummyCache'
'django.core.cache.backends.filebased.FileBasedCache'
'django.core.cache.backends.locmem.LocMemCache'
'django.core.cache.backends.memcached.PyMemcacheCache'
'django.core.cache.backends.memcached.PyLibMCCache'
'django.core.cache.backends.redis.RedisCache'
You can use a cache backend that doesn't ship with Django by setting\nBACKEND to a fully-qualified path of a cache\nbackend class (i.e. mypackage.backends.whatever.WhateverCache).
KEY_FUNCTIONLink to this heading#A string containing a dotted path to a function (or any callable) that defines how to\ncompose a prefix, version and key into a final cache key. The default\nimplementation is equivalent to the function:
\ndef make_key(key, key_prefix, version):\n return ':'.join([key_prefix, str(version), key])\nAnda dapat menggunakan fungsi kunci apapun anda inginkan, selama itu mempunyai tanda tangan argumen sama.
\nLihat cache documentation untuk informasi lebih.
\nKEY_PREFIXLink to this heading#Awalan: '' (String kosong)
Sebuah string yang akan otomatis disertakan (didahulukan secara awalan) untuk memangguk semua kunci penyimpanan sementara digunakan oleh peladen Django.
\nLihat cache documentation untuk informasi lebih.
\nLOCATIONLink to this heading#Awalan: '' (String kosong)
The location of the cache to use. This might be the directory for a\nfile system cache, a host and port for a memcache server, or an identifying\nname for a local memory cache. e.g.:
\nCACHES = {\n 'default': {\n 'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache',\n 'LOCATION': '/var/tmp/django_cache',\n }\n}\nOPTIONSLink to this heading#Awalan: None
Parameter tambahan untuk dilewatkan ke backend penyimpanan sementara. Parameter tersedia beragam bergantung pada backend penyimpanan sementara anda.
\nBeberapa informasi pada parameter tersedia dapat ditemukan dalam dokumentasi cache arguments. Untuk informasi lebih, obrolkan backend modul dokumentasi sendiri anda.
\nTIMEOUTLink to this heading#Awalan: 300
The number of seconds before a cache entry is considered stale. If the value of\nthis setting is None, cache entries will not expire. A value of 0\ncauses keys to immediately expire (effectively "don't cache").
VERSIONLink to this heading#Awalan: 1
Nomor versi awalan untuk kunci-kunci penyimpanan sementara dibangkitkan oleh peladen Django.
\nLihat the cache documentation untuk informasi lebih.
\nCACHE_MIDDLEWARE_ALIASLink to this heading#Awalan: 'default'
hubungan cache untuk digunakan untuk cache middleware.
\nCACHE_MIDDLEWARE_KEY_PREFIXLink to this heading#Awalan: '' (String kosong)
Sebuah string yang akan diawalan pada kunci penyimpanan sementara dibangkitkan oleh cache middleware. Awalan ini dipadukan dengan pengaturan KEY_PREFIX setting; itu tidak menggantinya.
CACHE_MIDDLEWARE_SECONDSLink to this heading#Awalan: 600
Jumlah detik untuk menyimpan sementara halaman untuk cache middleware.
\n\nCSRF_USE_SESSIONSLink to this heading#Awal: False
Apakah menyimpan token CSRF dalam sesi pengguna daripada dalam sebuah kue. Itu membutuhkan penggunaan django.contrib.sessions.
Menyimpan token CSRF dalam sebuah kue (awalan Django) adalah aman, tetapi menyimpan itu dalam sesi adalah praktik umum dalam kerangka kerja karingan lain dan oleh akrena itu terkadan diminta oleh pemeriksa keamanan.
\nSince the default error views require the CSRF token,\nSessionMiddleware must appear in\nMIDDLEWARE before any middleware that may raise an exception to\ntrigger an error view (such as PermissionDenied)\nif you're using CSRF_USE_SESSIONS. See Pengurutan middleware.
CSRF_FAILURE_VIEWLink to this heading#Awalan: 'django.views.csrf.csrf_failure'
Sebuah jalur bertitik untuk melihat fungsi untuk digunakan ketika permintaan datang ditolak oleh CSRF protection. Fungsi harus memiliki tanda tangan ini:
\ndef csrf_failure(request, reason=""):\n ...\ndimana reason adalah pesan pendek (diperuntukkan untuk pengembang atau pencatat, bukan untuk pengguna akhir) menunjukkan alasan permintaan telah ditolak. Itu harus mengembalikan sebuah HttpResponseForbidden.
django.views.csrf.csrf_failure() menerima sebuah tambahan parameter template_name yang awalan pada '403_csrf.html'. Jika sebuah cetakan dengan nama yang ada, itu akan digunakan membangun halaman.
CSRF_HEADER_NAMELink to this heading#Awalan: 'HTTP_X_CSRFTOKEN'
Nama dari kepala peminta digunakan untuk autentifikasi CSRF.
\nAs with other HTTP headers in request.META, the header name received from\nthe server is normalized by converting all characters to uppercase, replacing\nany hyphens with underscores, and adding an 'HTTP_' prefix to the name.\nFor example, if your client sends a 'X-XSRF-TOKEN' header, the setting\nshould be 'HTTP_X_XSRF_TOKEN'.
CSRF_TRUSTED_ORIGINSLink to this heading#Awalan: {} (Daftar kosong)
A list of trusted origins for unsafe requests (e.g. POST).
For requests that include the Origin header, Django's CSRF protection\nrequires that header match the origin present in the Host header.
For a secure unsafe\nrequest that doesn't include the Origin header, the request must have a\nReferer header that matches the origin present in the Host header.
These checks prevent, for example, a POST request from\nsubdomain.example.com from succeeding against api.example.com. If you\nneed cross-origin unsafe requests, continuing the example, add\n'https://subdomain.example.com' to this list (and/or http://... if\nrequests originate from an insecure page).
The setting also supports subdomains, so you could add\n'https://*.example.com', for example, to allow access from all subdomains\nof example.com.
DATABASESLink to this heading#Awalan: {} (Kamus kosong)
Sebuah dictionary mengandung pengaturan semua basisdata utnuk digunakan dengan Django. itu adalah dictionary bersarang yang isinya memetakan sebuah nama lain basisdata ke sebuah dictionary pilihan untuk sebuah basisdata sendiri.
\nPengaturan DATABASES harus mengkonfigurasi sebuah basisdata default; angka apapun dari basisdata tambahan mungkin juga ditentukan.
Kemungkinan berkas pengaturan sederhana adalah untuk pengaturan basisdata-tunggal menggunakan SQLite. Ini dapat dikonfigurasi menggunakan berikut:
\nDATABASES = {\n 'default': {\n 'ENGINE': 'django.db.backends.sqlite3',\n 'NAME': 'mydatabase',\n }\n}\nWhen connecting to other database backends, such as MariaDB, MySQL, Oracle, or\nPostgreSQL, additional connection parameters will be required. See\nthe ENGINE setting below on how to specify\nother database types. This example is for PostgreSQL:
DATABASES = {\n 'default': {\n 'ENGINE': 'django.db.backends.postgresql',\n 'NAME': 'mydatabase',\n 'USER': 'mydatabaseuser',\n 'PASSWORD': 'mypassword',\n 'HOST': '127.0.0.1',\n 'PORT': '5432',\n }\n}\nPilihan paling dalam berikut yang mungkin dibutuhkan untuk konfigurasi lebih lengkap tersedia:
\nATOMIC_REQUESTSLink to this heading#Awal: False
Setel ini menjadi True untuk membungkus setiap tampilan dalam transaksi pada basisdata ini. Lihat Mengikat transaksi pada permintaan HTTP.
AUTOCOMMITLink to this heading#Awal: True
Setel ini menjadi False jika anda ingin disable Django's transaction management dan menerapkan milik anda sendiri.
ENGINELink to this heading#Awalan: '' (String kosong)
Backend basisdata untuk digunakan. Backend basisdata siap-pakai adalah:
\n'django.db.backends.postgresql'
'django.db.backends.mysql'
'django.db.backends.sqlite3'
'django.db.backends.oracle'
Anda dapat menggunakan backend basisdata yang tidak dikirim dengan Django dengan mengatur ENGINE pada jalur sepenuhnya memenuhi syarat (yaitu mypackage.backends.whatever).
HOSTLink to this heading#Awalan: '' (String kosong)
Rumah mana digunakan ketika menghubungkan ke basisdata. Sebuah string kosong berarti localhost. Tidak digunakan dengan SQLite.
\nJika nilai ini dimulai dengan garis depan ('/') dan anda sedang menggunakan MySQL, MySQLakan terhubung melalui sebuah soket unix pada soket yang ditentukan. Sebagi contoh:
"HOST": '/var/run/mysql'\nJika anda menggunakan MySQL dan nilai ini tidak dimulai dengan garis miring depan, kemudian nilai ini dianggap menjadi rumah.
\nJika anda sedang menggunakan PostgreSQL, secara awalan (HOST kosong), hubungan ke baisdata selesai melalui soket ranah UNIX (baris-baris 'local' dalam pg_hba.conf). Jika soket ranah anda bukan tempat standar, gunakan nilai sama dari unix_socket_directory dari postgresql.conf. Jika anda ingin berhubungan melalui soket TCP, setel HOST pada 'localhost' atau '127.0.0.1' (baris-baris 'host' dalam pg_hba.conf). Pada Windows, anda harus selalu menentukan HOST, ketika soket ranah UNIX tidak tersedia.
NAMELink to this heading#Awalan: '' (String kosong)
Nama dari basisdata untuk digunakan. Untuk SQLite, itu adalah jalur penuh pada berkas basisdata. Ketika menentukan jalur, selalu gunakan garis miring depan, bahkan pada Windows (misalnya C:/homes/user/mysite/sqlite3.db`).
\nCONN_MAX_AGELink to this heading#Awal: 0
The lifetime of a database connection, as an integer of seconds. Use 0 to\nclose database connections at the end of each request — Django's historical\nbehavior — and None for unlimited persistent connections.
OPTIONSLink to this heading#Awalan: {} (Kamus kosong)
Parameter tambahan digunakan ketika berhubungan ke basisdata. Parameter tersedia beragam bergantung pada backend basisdata anda.
\nBeberapa informasi pada parameter tersedia dapat ditemukan dalam dokumentasi Database Backends. Untuk informasi lebih, rundingkan dokumentasi modul backend milik anda sendiri.
\nPASSWORDLink to this heading#Awalan: '' (String kosong)
Sandi anda gunakan ketika berhubungan ke basisdata. Tidak digunakan dengan SQLite.
\nPORTLink to this heading#Awalan: '' (String kosong)
Port digunakan ketika berhubungan ke basisdata. Sebuah string kosong berarti port awalan. Bukan digunakan dengan SQLite.
\nTIME_ZONELink to this heading#Awalan: None
A string representing the time zone for this database connection or None.\nThis inner option of the DATABASES setting accepts the same values\nas the general TIME_ZONE setting.
When USE_TZ is True and this option is set, reading datetimes\nfrom the database returns aware datetimes in this time zone instead of UTC.\nWhen USE_TZ is False, it is an error to set this option.
If the database backend doesn't support time zones (e.g. SQLite, MySQL,\nOracle), Django reads and writes datetimes in local time according to this\noption if it is set and in UTC if it isn't.
\nChanging the connection time zone changes how datetimes are read from and\nwritten to the database.
\nIf Django manages the database and you don't have a strong reason to do\notherwise, you should leave this option unset. It's best to store datetimes\nin UTC because it avoids ambiguous or nonexistent datetimes during daylight\nsaving time changes. Also, receiving datetimes in UTC keeps datetime\narithmetic simple — there's no need to consider potential offset changes\nover a DST transition.
If you're connecting to a third-party database that stores datetimes in a\nlocal time rather than UTC, then you must set this option to the\nappropriate time zone. Likewise, if Django manages the database but\nthird-party systems connect to the same database and expect to find\ndatetimes in local time, then you must set this option.
If the database backend supports time zones (e.g. PostgreSQL), the\nTIME_ZONE option is very rarely needed. It can be changed at any time;\nthe database takes care of converting datetimes to the desired time zone.
Setting the time zone of the database connection may be useful for running\nraw SQL queries involving date/time functions provided by the database, such\nas date_trunc, because their results depend on the time zone.
However, this has a downside: receiving all datetimes in local time makes\ndatetime arithmetic more tricky — you must account for possible offset\nchanges over DST transitions.
\nConsider converting to local time explicitly with AT TIME ZONE in raw SQL\nqueries instead of setting the TIME_ZONE option.
DISABLE_SERVER_SIDE_CURSORSLink to this heading#Awal: False
Setel ini menjadi True jika anda ingin meniadakan penggunaan kursor sisi-peladen dengan QuerySet.iterator(). Menggabungkan transaksi dan kursor sisi-peladen menggambarkan kasus penggunaan.
Ini adalah pengaturan tertentu-PostgreSQL.
\nUSERLink to this heading#Awalan: '' (String kosong)
Username untuk digunakan ketika berhubungan ke basisdata. Tidak digunakan dengan SQLite.
\nTESTLink to this heading#Awalan: {} (Kamus kosong)
Sebuah dictionary dari pengaturan untuk percobaan basisdata; untuk rincian lebih tentang pembuatan dan penggunakan percobaan basisdata, lihat Basisdata percobaan.
\nIni adalah sebuah contoh dengan konfigurasi basisdata percobaan:
\nDATABASES = {\n 'default': {\n 'ENGINE': 'django.db.backends.postgresql',\n 'USER': 'mydatabaseuser',\n 'NAME': 'mydatabase',\n 'TEST': {\n 'NAME': 'mytestdatabase',\n },\n },\n}\nKunci berikut dalam dictionary TEST tersedia:
CHARSETLink to this heading#Awalan: None
The character set encoding used to create the test database. The value of this\nstring is passed directly through to the database, so its format is\nbackend-specific.
\nDidukung oleh backend PostgreSQL (postgresql) dan MySQL (mysql).
COLLATIONLink to this heading#Awalan: None
The collation order to use when creating the test database. This value is\npassed directly to the backend, so its format is backend-specific.
\nHanya didukung untuk backend mysql (lihat MySQL manual untuk rincian).
DEPENDENCIESLink to this heading#Awalan: ['default'], untuk semua basisdata selain dari default, yang tidak mempunyai ketergantungan.
The creation-order dependencies of the database. See the documentation\non controlling the creation order of test databases for details.
\nMIGRATELink to this heading#Awal: True
When set to False, migrations won't run when creating the test database.\nThis is similar to setting None as a value in MIGRATION_MODULES,\nbut for all apps.
MIRRORLink to this heading#Awalan: None
Nama lain dari basisdata bahwa basisdata ini harus bercermin selama percobaan.
\nThis setting exists to allow for testing of primary/replica\n(referred to as master/slave by some databases)\nconfigurations of multiple databases. See the documentation on\ntesting primary/replica configurations for details.
\nNAMELink to this heading#Awalan: None
Nama dari basisdata untuk digunakan ketika menjalankan rangkaian percobaan.
\nIf the default value (None) is used with the SQLite database engine, the\ntests will use a memory resident database. For all other database engines the\ntest database will use the name 'test_' + DATABASE_NAME.
Lihat Basisdata percobaan.
\nSERIALIZELink to this heading#Boolean value to control whether or not the default test runner serializes the\ndatabase into an in-memory JSON string before running tests (used to restore\nthe database state between tests if you don't have transactions). You can set\nthis to False to speed up creation time if you don't have any test classes\nwith serialized_rollback=True.
TEMPLATELink to this heading#Ini adalah pengaturan tertentu-PostgreSQL.
\nThe name of a template (e.g. 'template0') from which to create the test\ndatabase.
CREATE_DBLink to this heading#Awal: True
Ini adalah sebuah pengaturan khusus-Oracle.
\nJika itu disetel menjadi False, tablespace percobaan tidak akan otomatis dibuat pada permulaan dari percobaan atau dijatuhkan pada akhir.
CREATE_USERLink to this heading#Awal: True
Ini adalah sebuah pengaturan khusus-Oracle.
\nJika ini disetel menjadi False, percobaan pengguna tidak akan otomatis dibuat pada akhiran dari percobaan dan dijatuhkan pada akhir.
USERLink to this heading#Awalan: None
Ini adalah sebuah pengaturan khusus-Oracle.
\nNama pengguna digunakan ketika berhubungan ke basisdata Oracle yang akan digunakan ketika menjalankan percobaan. Jika tidak disediakan, Django akan menggunakan 'test_' + USER.
PASSWORDLink to this heading#Awalan: None
Ini adalah sebuah pengaturan khusus-Oracle.
\nThe password to use when connecting to the Oracle database that will be used\nwhen running tests. If not provided, Django will generate a random password.
\nORACLE_MANAGED_FILESLink to this heading#Awal: False
Ini adalah sebuah pengaturan khusus-Oracle.
\nIf set to True, Oracle Managed Files (OMF) tablespaces will be used.\nDATAFILE and DATAFILE_TMP will be ignored.
TBLSPACELink to this heading#Awalan: None
Ini adalah sebuah pengaturan khusus-Oracle.
\nThe name of the tablespace that will be used when running tests. If not\nprovided, Django will use 'test_' + USER.
TBLSPACE_TMPLink to this heading#Awalan: None
Ini adalah sebuah pengaturan khusus-Oracle.
\nThe name of the temporary tablespace that will be used when running tests. If\nnot provided, Django will use 'test_' + USER + '_temp'.
DATAFILELink to this heading#Awalan: None
Ini adalah sebuah pengaturan khusus-Oracle.
\nThe name of the datafile to use for the TBLSPACE. If not provided, Django will\nuse TBLSPACE + '.dbf'.
DATAFILE_TMPLink to this heading#Awalan: None
Ini adalah sebuah pengaturan khusus-Oracle.
\nThe name of the datafile to use for the TBLSPACE_TMP. If not provided, Django\nwill use TBLSPACE_TMP + '.dbf'.
DATAFILE_MAXSIZELink to this heading#Awalan: '500M'
Ini adalah sebuah pengaturan khusus-Oracle.
\nUkuran maksimal yang DATAFILE izinkan untuk tumbuh.
\nDATAFILE_TMP_MAXSIZELink to this heading#Awalan: '500M'
Ini adalah sebuah pengaturan khusus-Oracle.
\nUkuran maksimal yang DATAFILE_TMP izinkan untuk tumbuh.
\nDATAFILE_SIZELink to this heading#Awalan: '50M'
Ini adalah sebuah pengaturan khusus-Oracle.
\nUkuran inisial dari DATAFILE.
\nDATAFILE_TMP_SIZELink to this heading#Awalan: '50M'
Ini adalah sebuah pengaturan khusus-Oracle.
\nUkuran inisial dari DATAFILE_TMP.
\nDATAFILE_EXTSIZELink to this heading#Awalan: '25M'
Ini adalah sebuah pengaturan khusus-Oracle.
\nJumlah dimana DATAFILE diperpanjang ketika ruang lebih dubutuhkan.
\nDATAFILE_TMP_EXTSIZELink to this heading#Awalan: '25M'
Ini adalah sebuah pengaturan khusus-Oracle.
\nJumlah dari DATAFILE_TMP diperpanjang ketika ruang lebih dibutuhkan.
\nDATA_UPLOAD_MAX_MEMORY_SIZELink to this heading#Awalan: 2621440 (yaitu 2.5 MB).
The maximum size in bytes that a request body may be before a\nSuspiciousOperation (RequestDataTooBig) is\nraised. The check is done when accessing request.body or request.POST\nand is calculated against the total request size excluding any file upload\ndata. You can set this to None to disable the check. Applications that are\nexpected to receive unusually large form posts should tune this setting.
The amount of request data is correlated to the amount of memory needed to\nprocess the request and populate the GET and POST dictionaries. Large requests\ncould be used as a denial-of-service attack vector if left unchecked. Since web\nservers don't typically perform deep request inspection, it's not possible to\nperform a similar check at that level.
\nLihat juga FILE_UPLOAD_MAX_MEMORY_SIZE.
DATA_UPLOAD_MAX_NUMBER_FIELDSLink to this heading#Awalan: 1000
The maximum number of parameters that may be received via GET or POST before a\nSuspiciousOperation (TooManyFields) is\nraised. You can set this to None to disable the check. Applications that\nare expected to receive an unusually large number of form fields should tune\nthis setting.
The number of request parameters is correlated to the amount of time needed to\nprocess the request and populate the GET and POST dictionaries. Large requests\ncould be used as a denial-of-service attack vector if left unchecked. Since web\nservers don't typically perform deep request inspection, it's not possible to\nperform a similar check at that level.
\nDATA_UPLOAD_MAX_NUMBER_FILESLink to this heading#Default: 100
The maximum number of files that may be received via POST in a\nmultipart/form-data encoded request before a\nSuspiciousOperation (TooManyFiles) is\nraised. You can set this to None to disable the check. Applications that\nare expected to receive an unusually large number of file fields should tune\nthis setting.
The number of accepted files is correlated to the amount of time and memory\nneeded to process the request. Large requests could be used as a\ndenial-of-service attack vector if left unchecked. Since web servers don't\ntypically perform deep request inspection, it's not possible to perform a\nsimilar check at that level.
\nDATABASE_ROUTERSLink to this heading#Awalan: {} (Daftar kosong)
The list of routers that will be used to determine which database\nto use when performing a database query.
\nLihat dokumentasi pada automatic database routing in multi database configurations.
\nDATE_FORMATLink to this heading#Awalan: 'N j, Y' (misalnya Feb. 4, 2003)
The default formatting to use for displaying date fields in any part of the\nsystem. Note that if USE_L10N is set to True, then the\nlocale-dictated format has higher precedence and will be applied instead. See\nallowed date format strings.
Lihat juga DATETIME_FORMAT, TIME_FORMAT dan SHORT_DATE_FORMAT.
DATE_INPUT_FORMATSLink to this heading#Awal:
\n[\n '%Y-%m-%d', # '2006-10-25'\n '%m/%d/%Y', # '10/25/2006'\n '%m/%d/%y', # '10/25/06'\n '%b %d %Y', # 'Oct 25 2006'\n '%b %d, %Y', # 'Oct 25, 2006'\n '%d %b %Y', # '25 Oct 2006'\n '%d %b, %Y', # '25 Oct, 2006'\n '%B %d %Y', # 'October 25 2006'\n '%B %d, %Y', # 'October 25, 2006'\n '%d %B %Y', # '25 October 2006'\n '%d %B, %Y', # '25 October, 2006'\n]\nA list of formats that will be accepted when inputting data on a date field.\nFormats will be tried in order, using the first valid one. Note that these\nformat strings use Python's datetime module syntax, not the format strings from the date\ntemplate filter.
When USE_L10N is True, the locale-dictated format has higher\nprecedence and will be applied instead.
Lihat juga DATETIME_INPUT_FORMATS dan TIME_INPUT_FORMATS.
DATETIME_FORMATLink to this heading#Awalan: 'N j, Y, P' (misalnya Feb. 4, 2003, 4 p.m.)
The default formatting to use for displaying datetime fields in any part of the\nsystem. Note that if USE_L10N is set to True, then the\nlocale-dictated format has higher precedence and will be applied instead. See\nallowed date format strings.
Lihat juga DATE_FORMAT, TIME_FORMAT dan SHORT_DATETIME_FORMAT.
DATETIME_INPUT_FORMATSLink to this heading#Awal:
\n[\n '%Y-%m-%d %H:%M:%S', # '2006-10-25 14:30:59'\n '%Y-%m-%d %H:%M:%S.%f', # '2006-10-25 14:30:59.000200'\n '%Y-%m-%d %H:%M', # '2006-10-25 14:30'\n '%m/%d/%Y %H:%M:%S', # '10/25/2006 14:30:59'\n '%m/%d/%Y %H:%M:%S.%f', # '10/25/2006 14:30:59.000200'\n '%m/%d/%Y %H:%M', # '10/25/2006 14:30'\n '%m/%d/%y %H:%M:%S', # '10/25/06 14:30:59'\n '%m/%d/%y %H:%M:%S.%f', # '10/25/06 14:30:59.000200'\n '%m/%d/%y %H:%M', # '10/25/06 14:30'\n]\nA list of formats that will be accepted when inputting data on a datetime\nfield. Formats will be tried in order, using the first valid one. Note that\nthese format strings use Python's datetime module syntax, not the format strings from the date\ntemplate filter. Date-only formats are not included as datetime fields will\nautomatically try DATE_INPUT_FORMATS in last resort.
When USE_L10N is True, the locale-dictated format has higher\nprecedence and will be applied instead.
Lihat juga DATE_INPUT_FORMATS dan TIME_INPUT_FORMATS.
DEBUGLink to this heading#Awal: False
Boolean yang menyalakan/mematikan suasana mencari kesalahan.
\nJangan pernah menyebarkan situs kedalam kedalam produksi dengan DEBUG menyala.
One of the main features of debug mode is the display of detailed error pages.\nIf your app raises an exception when DEBUG is True, Django will\ndisplay a detailed traceback, including a lot of metadata about your\nenvironment, such as all the currently defined Django settings (from\nsettings.py).
As a security measure, Django will not include settings that might be\nsensitive, such as SECRET_KEY. Specifically, it will exclude any\nsetting whose name includes any of the following:
'API'
'KEY'
'PASS'
'SECRET'
'SIGNATURE'
'TOKEN'
Note that these are partial matches. 'PASS' will also match PASSWORD,\njust as 'TOKEN' will also match TOKENIZED and so on.
Still, note that there are always going to be sections of your debug output\nthat are inappropriate for public consumption. File paths, configuration\noptions and the like all give attackers extra information about your server.
\nIt is also important to remember that when running with DEBUG\nturned on, Django will remember every SQL query it executes. This is useful\nwhen you're debugging, but it'll rapidly consume memory on a production server.
Finally, if DEBUG is False, you also need to properly set\nthe ALLOWED_HOSTS setting. Failing to do so will result in all\nrequests being returned as "Bad Request (400)".
DEBUG_PROPAGATE_EXCEPTIONSLink to this heading#Awal: False
If set to True, Django's exception handling of view functions\n(handler500, or the debug view if DEBUG\nis True) and logging of 500 responses (django.request) is\nskipped and exceptions propagate upward.
This can be useful for some test setups. It shouldn't be used on a live site\nunless you want your web server (instead of Django) to generate "Internal\nServer Error" responses. In that case, make sure your server doesn't show the\nstack trace or other sensitive information in the response.
\nDECIMAL_SEPARATORLink to this heading#Awalan: '.' (Titik)
Pemisah desimal awalan digunakan ketika membentuk angka desimal.
\nNote that if USE_L10N is set to True, then the locale-dictated\nformat has higher precedence and will be applied instead.
Lihat juga NUMBER_GROUPING, THOUSAND_SEPARATOR dan USE_THOUSAND_SEPARATOR.
DEFAULT_AUTO_FIELDLink to this heading#Awalan: 'django.db.models.AutoField'
Default primary key field type to use for models that don't have a field with\nprimary_key=True.
DEFAULT_CHARSETLink to this heading#Awalan: 'utf-8'
Default charset to use for all HttpResponse objects, if a MIME type isn't\nmanually specified. Used when constructing the Content-Type header.
DEFAULT_EXCEPTION_REPORTERLink to this heading#Awalan: 'django.views.debug.ExceptionReporter'
Default exception reporter class to be used if none has been assigned to the\nHttpRequest instance yet. See\nPenyesuaian laporan kesalahan.
DEFAULT_EXCEPTION_REPORTER_FILTERLink to this heading#Awalan: 'django.views.debug.SafeExceptionReporterFilter'
Default exception reporter filter class to be used if none has been assigned to\nthe HttpRequest instance yet.\nSee Filtering error reports.
DEFAULT_FILE_STORAGELink to this heading#Awalan: 'django.core.files.storage.FileSystemStorage'
Kelas penyimpanan berkas awalan untuk digunakan untuk tindakan terkait-berkas apapun yang tidak menentukan sistem penyimpanan tertentu. Lihat Mengelola berkas.
\nDEFAULT_FROM_EMAILLink to this heading#Awalan: 'webmaster@localhost'
Default email address to use for various automated correspondence from the\nsite manager(s). This doesn't include error messages sent to ADMINS\nand MANAGERS; for that, see SERVER_EMAIL.
DEFAULT_INDEX_TABLESPACELink to this heading#Awalan: '' (String kosong)
Tablespace awalan digunakan untuk pengindeksan pada bidang yang belum ditentukan, jika backend mendukung itu (lihat Tablespaces).
\nDEFAULT_TABLESPACELink to this heading#Awalan: '' (String kosong)
Tablespace awalan digunakan untuk model yang belum ditentukan, jika backend mendukung itu (lihat Tablespaces).
\nDISALLOWED_USER_AGENTSLink to this heading#Awalan: {} (Daftar kosong)
List of compiled regular expression objects representing User-Agent strings\nthat are not allowed to visit any page, systemwide. Use this for bots/crawlers.\nThis is only used if CommonMiddleware is installed (see\nMiddleware).
EMAIL_BACKENDLink to this heading#Awalan: 'django.core.mail.backends.smtp.EmailBackend'
Backend digunakan untuk mengirim surel. Untuk daftar dari backend tersedia lihat Mengirim surel.
\nEMAIL_FILE_PATHLink to this heading#Awalan: Tidak ditentukan
\nThe directory used by the file email backend\nto store output files.
\nEMAIL_HOSTLink to this heading#Awalan: 'localhost'
Rumah digunakan untuk mengirim surel.
\nLihat juga EMAIL_PORT.
EMAIL_HOST_PASSWORDLink to this heading#Awalan: '' (String kosong)
Password to use for the SMTP server defined in EMAIL_HOST. This\nsetting is used in conjunction with EMAIL_HOST_USER when\nauthenticating to the SMTP server. If either of these settings is empty,\nDjango won't attempt authentication.
Lihat juga EMAIL_HOST_USER.
EMAIL_HOST_USERLink to this heading#Awalan: '' (String kosong)
Nama pengguna untuk digunakan pada peladen SMTP ditentukan dalam EMAIL_HOST. Jika kosong, Django tidak akan berusaha mengecek.
Lihat juga EMAIL_HOST_PASSWORD.
EMAIL_PORTLink to this heading#Awalan: 25
Port digunakan untuk peladen SMTP ditentukan dalam EMAIL_HOST.
EMAIL_SUBJECT_PREFIXLink to this heading#Awalan: '[Django] '
Subject-line prefix for email messages sent with django.core.mail.mail_admins\nor django.core.mail.mail_managers. You'll probably want to include the\ntrailing space.
EMAIL_USE_LOCALTIMELink to this heading#Awal: False
Apakah mengirim kepala Date SMTP dari pesan surel dalam zona waktu lokal (True) atau dalam UTC (False).
EMAIL_USE_TLSLink to this heading#Awal: False
Whether to use a TLS (secure) connection when talking to the SMTP server.\nThis is used for explicit TLS connections, generally on port 587. If you are\nexperiencing hanging connections, see the implicit TLS setting\nEMAIL_USE_SSL.
EMAIL_USE_SSLLink to this heading#Awal: False
Whether to use an implicit TLS (secure) connection when talking to the SMTP\nserver. In most email documentation this type of TLS connection is referred\nto as SSL. It is generally used on port 465. If you are experiencing problems,\nsee the explicit TLS setting EMAIL_USE_TLS.
Note that EMAIL_USE_TLS/EMAIL_USE_SSL are mutually\nexclusive, so only set one of those settings to True.
EMAIL_SSL_CERTFILELink to this heading#Awalan: None
If EMAIL_USE_SSL or EMAIL_USE_TLS is True, you can\noptionally specify the path to a PEM-formatted certificate chain file to use\nfor the SSL connection.
EMAIL_SSL_KEYFILELink to this heading#Awalan: None
If EMAIL_USE_SSL or EMAIL_USE_TLS is True, you can\noptionally specify the path to a PEM-formatted private key file to use for the\nSSL connection.
Note that setting EMAIL_SSL_CERTFILE and EMAIL_SSL_KEYFILE\ndoesn't result in any certificate checking. They're passed to the underlying SSL\nconnection. Please refer to the documentation of Python's\npython:ssl.wrap_socket() function for details on how the certificate chain\nfile and private key file are handled.
EMAIL_TIMEOUTLink to this heading#Awalan: None
Menentukan waktu habis dalam detik untuk memblok tindakan seperti usaha berhubungan.
\nFILE_UPLOAD_HANDLERSLink to this heading#Awal:
\n[\n 'django.core.files.uploadhandler.MemoryFileUploadHandler',\n 'django.core.files.uploadhandler.TemporaryFileUploadHandler',\n]\nA list of handlers to use for uploading. Changing this setting allows complete\ncustomization -- even replacement -- of Django's upload process.
\nLihat Mengelola berkas untuk rincian.
\nFILE_UPLOAD_MAX_MEMORY_SIZELink to this heading#Awalan: 2621440 (yaitu 2.5 MB).
The maximum size (in bytes) that an upload will be before it gets streamed to\nthe file system. See Mengelola berkas for details.
\nLihat juga DATA_UPLOAD_MAX_MEMORY_SIZE.
FILE_UPLOAD_DIRECTORY_PERMISSIONSLink to this heading#Awalan: None
The numeric mode to apply to directories created in the process of uploading\nfiles.
\nThis setting also determines the default permissions for collected static\ndirectories when using the collectstatic management command. See\ncollectstatic for details on overriding it.
This value mirrors the functionality and caveats of the\nFILE_UPLOAD_PERMISSIONS setting.
FILE_UPLOAD_PERMISSIONSLink to this heading#Awalan: 0o644
The numeric mode (i.e. 0o644) to set newly uploaded files to. For\nmore information about what these modes mean, see the documentation for\nos.chmod().
If None, you'll get operating-system dependent behavior. On most platforms,\ntemporary files will have a mode of 0o600, and files saved from memory will\nbe saved using the system's standard umask.
For security reasons, these permissions aren't applied to the temporary files\nthat are stored in FILE_UPLOAD_TEMP_DIR.
This setting also determines the default permissions for collected static files\nwhen using the collectstatic management command. See\ncollectstatic for details on overriding it.
FILE_UPLOAD_TEMP_DIRLink to this heading#Awalan: None
The directory to store data to (typically files larger than\nFILE_UPLOAD_MAX_MEMORY_SIZE) temporarily while uploading files.\nIf None, Django will use the standard temporary directory for the operating\nsystem. For example, this will default to /tmp on *nix-style operating\nsystems.
Lihat Mengelola berkas untuk rincian.
\nFIRST_DAY_OF_WEEKLink to this heading#Awalan: 0 (Minggu)
A number representing the first day of the week. This is especially useful\nwhen displaying a calendar. This value is only used when not using\nformat internationalization, or when a format cannot be found for the\ncurrent locale.
\nNilai harus berupa integer 0 sampai 6, dimana 0 berarti Minggu, 1 berarti Senin dan seterusnya.
\nFIXTURE_DIRSLink to this heading#Awalan: {} (Daftar kosong)
List of directories searched for fixture files, in addition to the\nfixtures directory of each application, in search order.
Catat bahwa jalur-jalur ini harus menggunakan garis miring didepan gaya-Unix, bahkan pada Windows.
\nLihat Menyediakan data dengan perlengkapan dan Fixture loading.
\nFORCE_SCRIPT_NAMELink to this heading#Awalan: None
If not None, this will be used as the value of the SCRIPT_NAME\nenvironment variable in any HTTP request. This setting can be used to override\nthe server-provided value of SCRIPT_NAME, which may be a rewritten version\nof the preferred value or not supplied at all. It is also used by\ndjango.setup() to set the URL resolver script prefix outside of the\nrequest/response cycle (e.g. in management commands and standalone scripts) to\ngenerate correct URLs when SCRIPT_NAME is not /.
FORM_RENDERERLink to this heading#Awalan: 'django.forms.renderers.DjangoTemplates'
The class that renders forms and form widgets. It must implement\nthe low-level render API. Included form\nrenderers are:
\n\nFORMAT_MODULE_PATHLink to this heading#Awalan: None
A full Python path to a Python package that contains custom format definitions\nfor project locales. If not None, Django will check for a formats.py\nfile, under the directory named as the current locale, and will use the\nformats defined in this file.
Sebagai contoh, jika FORMAT_MODULE_PATH disetel ke mysite.formats, dan bahasa saat ini adalah en (Inggris), Django akan mengaharpkan pohon direktori seperti:
mysite/\n formats/\n __init__.py\n en/\n __init__.py\n formats.py\nAnda dapat juga mensetel pengaturan ini pada daftar jalur Python, sebagai contoh:
\nFORMAT_MODULE_PATH = [\n 'mysite.formats',\n 'some_app.formats',\n]\nWhen Django searches for a certain format, it will go through all given Python\npaths until it finds a module that actually defines the given format. This\nmeans that formats defined in packages farther up in the list will take\nprecedence over the same formats in packages farther down.
\nBentuk tersedia adalah:
\n\nIGNORABLE_404_URLSLink to this heading#Awalan: {} (Daftar kosong)
List of compiled regular expression objects describing URLs that should be\nignored when reporting HTTP 404 errors via email (see\nHow to manage error reporting). Regular expressions are matched against\nrequest's full paths (including\nquery string, if any). Use this if your site does not provide a commonly\nrequested file such as favicon.ico or robots.txt.
Ini hanya digunakan jika BrokenLinkEmailsMiddleware diadakan (lihat Middleware).
INSTALLED_APPSLink to this heading#Awalan: {} (Daftar kosong)
A list of strings designating all applications that are enabled in this\nDjango installation. Each string should be a dotted Python path to:
\nsebuah kelas konfigurasi aplikasi (disukai), atau
paket mengandung sebuah aplikasi.
Learn more about application configurations.
\n\n\nWhen several applications provide different versions of the same resource\n(template, static file, management command, translation), the application\nlisted first in INSTALLED_APPS has precedence.
INTERNAL_IPSLink to this heading#Awalan: {} (Daftar kosong)
Daftar dari alamat IP, sebagai string, yaitu:
\nMengijinkan debug() pengolah konteks untuk menambah beberapa variabel pada konteks cetakan.
Dapat menggunakan admindocs bookmarklets bahkan jika tidak masuk sebagai pengguna staf.
Ditandai sebagai "internal" (berlawanan dengan "EXTERNAL") dalam surel AdminEmailHandler.
LANGUAGE_CODELink to this heading#Awalan: 'en-us'
Strign mewakili kode bahasa untuk pemasangan ini. Ini harus berupa language ID format. Sebagai contoh, U.S. English adalah "en-us". Lihat juga list of language identifiers dan Internasionalisasi dan lokalisasi.
USE_I18N harus aktif untuk pengaturan ini untuk memberikan pengaruh.
Itu melayani dua tujuan:
\nJika middleware lokal tidak digunakan, itu memutuskan terjemahan mana dilayani ke semua pengguna.
If the locale middleware is active, it provides a fallback language in case the\nuser's preferred language can't be determined or is not supported by the\nwebsite. It also provides the fallback translation when a translation for a\ngiven literal doesn't exist for the user's preferred language.
Lihat Bagaimana Django menemukan pilihan bahasa untuk rincian lebih.
\nLANGUAGESLink to this heading#Default: A list of all available languages. This list is continually growing\nand including a copy here would inevitably become rapidly out of date. You can\nsee the current list of translated languages by looking in\ndjango/conf/global_settings.py.
\nThe list is a list of two-tuples in the format\n(language code, language name) -- for example,\n('ja', 'Japanese').\nThis specifies which languages are available for language selection. See\nInternasionalisasi dan lokalisasi.
Generally, the default value should suffice. Only set this setting if you want\nto restrict language selection to a subset of the Django-provided languages.
\nJika anda menentukan sebuah penyesuaian pengaturan LANGUAGES, anda dapat menandai nama-nama bahasa sebagari string terjemahan menggunakan fungsi gettext_lazy().
Ini adalah contoh sebuah berkas pengaturan:
\nfrom django.utils.translation import gettext_lazy as _\n\nLANGUAGES = [\n ('de', _('German')),\n ('en', _('English')),\n]\nLANGUAGES_BIDILink to this heading#Default: A list of all language codes that are written right-to-left. You can\nsee the current list of these languages by looking in\ndjango/conf/global_settings.py.
\nDaftar mengandung language codes untuk bahasa yang ditulis dari kiri-ke-kanan.
\nGenerally, the default value should suffice. Only set this setting if you want\nto restrict language selection to a subset of the Django-provided languages.\nIf you define a custom LANGUAGES setting, the list of bidirectional\nlanguages may contain language codes which are not enabled on a given site.
LOCALE_PATHSLink to this heading#Awalan: {} (Daftar kosong)
Sebuah daftar direktori dimana Django mencari berkas terjemahan. Lihat Bagaimana Django menemukan terjemahan.
\nContoh:
\nLOCALE_PATHS = [\n '/home/www/project/common_files/locale',\n '/var/local/translations/locale',\n]\nDjango akan mencari dalam setiap jalur ini untuk direktori <locale_code>/LC_MESSAGES mengandung berkas terjemahan sebenarnya.
LOGGINGLink to this heading#Awalan Sebuah dictionary konfigurasi pencatatan
\nA data structure containing configuration information. The contents of\nthis data structure will be passed as the argument to the\nconfiguration method described in LOGGING_CONFIG.
Among other things, the default logging configuration passes HTTP 500 server\nerrors to an email log handler when DEBUG is False. See also\nMengkonfigurasi catatan.
Anda dapat melihat konfigurasi pencatatan awalan dengan mencari dalam django/utils/log.py.
\nLOGGING_CONFIGLink to this heading#Awalan: 'logging.config.dictConfig'
A path to a callable that will be used to configure logging in the\nDjango project. Points at an instance of Python's dictConfig configuration method by default.
\nJika anda tidak mensetel LOGGING_CONFIG menjadi None, pengolahan konfigurasi pencatatan akan dilewatkan.
MANAGERSLink to this heading#Awalan: {} (Daftar kosong)
A list in the same format as ADMINS that specifies who should get\nbroken link notifications when\nBrokenLinkEmailsMiddleware is enabled.
MEDIA_ROOTLink to this heading#Awalan: '' (String kosong)
Jalur sistem berkas mutlak pada direktori yang akan menahan user-uploaded files.
\nContoh: "/var/www/example.com/media/"
Lihat juga MEDIA_URL.
MEDIA_URLLink to this heading#Awalan: '' (String kosong)
URL yang menangani media dilayani dari MEDIA_ROOT, digunakan untuk managing stored files 1. Itu harus berakhir dalam sebuah garis miring jika menyetel ke nilai bukan-kosong. Anda akan butuh configure these files to be served 2 dalam kedua lingkungan pengembangan dan produksi.
Jika anda ingin menggunakan {{ MEDIA_URL }} dalam cetakan-cetakan anda, tambah 'django.template.context_processors.media' dalam pilihan 'context_processors' dari TEMPLATES.
Contoh: "http://media.example.com/"
MIDDLEWARELink to this heading#Awalan: None
daftar dari middleware untuk digunakan. Lihat Middleware.
\nMIGRATION_MODULESLink to this heading#Awalan: {} (Kamus kosong)
A dictionary specifying the package where migration modules can be found on a\nper-app basis. The default value of this setting is an empty dictionary, but\nthe default package name for migration modules is migrations.
Contoh:
\n{'blog': 'blog.db_migrations'}\nIn this case, migrations pertaining to the blog app will be contained in\nthe blog.db_migrations package.
Jika anda menyediakan argumen app_label, makemigrations akan otomatis membuat paket jika itu belum ada.
When you supply None as a value for an app, Django will consider the app as\nan app without migrations regardless of an existing migrations submodule.\nThis can be used, for example, in a test settings file to skip migrations while\ntesting (tables will still be created for the apps' models). To disable\nmigrations for all apps during tests, you can set the\nMIGRATE to False instead. If\nMIGRATION_MODULES is used in your general project settings, remember to use\nthe migrate --run-syncdb option if you want to create tables for the\napp.
MONTH_DAY_FORMATLink to this heading#Awalan: 'F j'
The default formatting to use for date fields on Django admin change-list\npages -- and, possibly, by other parts of the system -- in cases when only the\nmonth and day are displayed.
\nFor example, when a Django admin change-list page is being filtered by a date\ndrilldown, the header for a given day displays the day and month. Different\nlocales have different formats. For example, U.S. English would say\n"January 1," whereas Spanish might say "1 Enero."
\nCatat bahwa jika USE_L10N disetel menjadi True, kemudian bentuk sesuai lokal-yang-ditentukan memiliki hak lebih tinggi dan akan diberlakukan.
Lihat allowed date format strings. Lihat juga DATE_FORMAT, DATETIME_FORMAT, TIME_FORMAT dan YEAR_MONTH_FORMAT.
NUMBER_GROUPINGLink to this heading#Awal: 0
Sejumlah angka dikelompokkan bersama-sama pada bagian integer dari sebuah angka.
\nCommon use is to display a thousand separator. If this setting is 0, then\nno grouping will be applied to the number. If this setting is greater than\n0, then THOUSAND_SEPARATOR will be used as the separator between\nthose groups.
Some locales use non-uniform digit grouping, e.g. 10,00,00,000 in\nen_IN. For this case, you can provide a sequence with the number of digit\ngroup sizes to be applied. The first number defines the size of the group\npreceding the decimal delimiter, and each number that follows defines the size\nof preceding groups. If the sequence is terminated with -1, no further\ngrouping is performed. If the sequence terminates with a 0, the last group\nsize is used for the remainder of the number.
Contoh tuple untuk en_IN:
NUMBER_GROUPING = (3, 2, 0)\nNote that if USE_L10N is set to True, then the locale-dictated\nformat has higher precedence and will be applied instead.
Lihat juga DECIMAL_SEPARATOR, THOUSAND_SEPARATOR dan USE_THOUSAND_SEPARATOR.
PREPEND_WWWLink to this heading#Awal: False
Apakah untuk menambahkan subranah "www." ke URL yang tidak memilikinya. Ini hanya digunakan jika CommonMiddleware terpasang (lihat Middleware). Lihat juga APPEND_SLASH.
ROOT_URLCONFLink to this heading#Awalan: Tidak ditentukan
\nA string representing the full Python import path to your root URLconf, for\nexample "mydjangoapps.urls". Can be overridden on a per-request basis by\nsetting the attribute urlconf on the incoming HttpRequest\nobject. See Bagaimana Django mengolah permintaan for details.
SECRET_KEYLink to this heading#Awalan: '' (String kosong)
A secret key for a particular Django installation. This is used to provide\ncryptographic signing, and should be set to a unique,\nunpredictable value.
\ndjango-admin startproject otomatis menambah SECRET_KEY dibangkitkan-acak ke setiap proyek baru.
Uses of the key shouldn't assume that it's text or bytes. Every use should go\nthrough force_str() or\nforce_bytes() to convert it to the desired type.
Django akan menolak dimulai jika SECRET_KEY tidak disetel.
Kunci rahasia digunakan untuk:
\nAll sessions if you are using\nany other session backend than django.contrib.sessions.backends.cache,\nor are using the default\nget_session_auth_hash().
All messages if you are using\nCookieStorage or\nFallbackStorage.
Semua token PasswordResetView .
Penggunaan apapun dari cryptographic signing, meskipun kunci berbeda disediakan.
Jika anda memutar kunci rahasia anda, semua diatas akan tidak sah. Kunci-kunci rahasia tidak digunakan untuk sandi dari pengguna dan perputaran kunci tidak akan mempengaruhi mereka.
\n\nSECURE_CONTENT_TYPE_NOSNIFFLink to this heading#Awal: True
Jika True, SecurityMiddleware mesetel kepala X-Content-Type-Options: nosniff pada semua tanggapan yang belum memiliki itu.
SECURE_CROSS_ORIGIN_OPENER_POLICYLink to this heading#Awalan: 'same-origin'
Unless set to None, the\nSecurityMiddleware sets the\nCross-Origin Opener Policy header on all responses that do not already\nhave it to the value provided.
SECURE_HSTS_INCLUDE_SUBDOMAINSLink to this heading#Awal: False
If True, the SecurityMiddleware adds\nthe includeSubDomains directive to the HTTP Strict Transport Security\nheader. It has no effect unless SECURE_HSTS_SECONDS is set to a\nnon-zero value.
SECURE_HSTS_PRELOADLink to this heading#Awal: False
If True, the SecurityMiddleware adds\nthe preload directive to the HTTP Strict Transport Security\nheader. It has no effect unless SECURE_HSTS_SECONDS is set to a\nnon-zero value.
SECURE_HSTS_SECONDSLink to this heading#Awal: 0
If set to a non-zero integer value, the\nSecurityMiddleware sets the\nHTTP Strict Transport Security header on all responses that do not\nalready have it.
SECURE_PROXY_SSL_HEADERLink to this heading#Awalan: None
A tuple representing an HTTP header/value combination that signifies a request\nis secure. This controls the behavior of the request object's is_secure()\nmethod.
By default, is_secure() determines if a request is secure by confirming\nthat a requested URL uses https://. This method is important for Django's\nCSRF protection, and it may be used by your own code or third-party apps.
If your Django app is behind a proxy, though, the proxy may be "swallowing"\nwhether the original request uses HTTPS or not. If there is a non-HTTPS\nconnection between the proxy and Django then is_secure() would always\nreturn False -- even for requests that were made via HTTPS by the end user.\nIn contrast, if there is an HTTPS connection between the proxy and Django then\nis_secure() would always return True -- even for requests that were\nmade originally via HTTP.
In this situation, configure your proxy to set a custom HTTP header that tells\nDjango whether the request came in via HTTPS, and set\nSECURE_PROXY_SSL_HEADER so that Django knows what header to look for.
Setel sebuah tuple dengan dua unsur -- nama dari kepala untuk mencari dan nilai diwajibkan. Sebagai contoh:
\nSECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')\nThis tells Django to trust the X-Forwarded-Proto header that comes from our\nproxy, and any time its value is 'https', then the request is guaranteed to\nbe secure (i.e., it originally came in via HTTPS).
You should only set this setting if you control your proxy or have some other\nguarantee that it sets/strips this header appropriately.
\nNote that the header needs to be in the format as used by request.META --\nall caps and likely starting with HTTP_. (Remember, Django automatically\nadds 'HTTP_' to the start of x-header names before making the header\navailable in request.META.)
SECURE_REDIRECT_EXEMPTLink to this heading#Awalan: {} (Daftar kosong)
If a URL path matches a regular expression in this list, the request will not be\nredirected to HTTPS. The\nSecurityMiddleware strips leading slashes\nfrom URL paths, so patterns shouldn't include them, e.g.\nSECURE_REDIRECT_EXEMPT = [r'^no-ssl/$', …]. If\nSECURE_SSL_REDIRECT is False, this setting has no effect.
SECURE_REFERRER_POLICYLink to this heading#Awalan: 'same-origin'
If configured, the SecurityMiddleware sets\nthe Referrer Policy header on all responses that do not already have it\nto the value provided.
SECURE_SSL_HOSTLink to this heading#Awalan: None
If a string (e.g. secure.example.com), all SSL redirects will be directed\nto this host rather than the originally-requested host\n(e.g. www.example.com). If SECURE_SSL_REDIRECT is False, this\nsetting has no effect.
SECURE_SSL_REDIRECTLink to this heading#Awal: False
If True, the SecurityMiddleware\nredirects all non-HTTPS requests to HTTPS (except for\nthose URLs matching a regular expression listed in\nSECURE_REDIRECT_EXEMPT).
SERIALIZATION_MODULESLink to this heading#Awalan: Tidak ditentukan
\nA dictionary of modules containing serializer definitions (provided as\nstrings), keyed by a string identifier for that serialization type. For\nexample, to define a YAML serializer, use:
\nSERIALIZATION_MODULES = {'yaml': 'path.to.yaml_serializer'}\nSERVER_EMAILLink to this heading#Awal: 'root@localhost'
The email address that error messages come from, such as those sent to\nADMINS and MANAGERS.
SHORT_DATE_FORMATLink to this heading#Awalan: 'm/d/Y' (misalnya 12/31/2003)
An available formatting that can be used for displaying date fields on\ntemplates. Note that if USE_L10N is set to True, then the\ncorresponding locale-dictated format has higher precedence and will be applied.\nSee allowed date format strings.
Lihat juga DATE_FORMAT dan SHORT_DATETIME_FORMAT.
SHORT_DATETIME_FORMATLink to this heading#Awalan: 'm/d/Y P' (misalnya 12/31/2003 4 p.m.)
An available formatting that can be used for displaying datetime fields on\ntemplates. Note that if USE_L10N is set to True, then the\ncorresponding locale-dictated format has higher precedence and will be applied.\nSee allowed date format strings.
Lihat juga DATE_FORMAT dan SHORT_DATE_FORMAT.
SIGNING_BACKENDLink to this heading#Awalan: 'django.core.signing.TimestampSigner'
Backend digunakan unntuk tandatangan kue dan data lain.
\nLihat juga dokumentasi Penandatanganan Kriptrograpi.
\nSILENCED_SYSTEM_CHECKSLink to this heading#Awalan: {} (Daftar kosong)
Sebuah daftar penciri dari pesan-pesan dibangkitkan oleh kerangka sistem pemeriksaan (yaitu ["models.W001"]`) yang anda harapkan secara tetap mengakui dan mengabaikan. Pemeriksaan diam-diam tidak akan dikeluarkan ke konsol.
\nLihat juga dokumentasi Kerangka pemeriksaan sistem.
\nTEMPLATESLink to this heading#Awalan: {} (Daftar kosong)
A list containing the settings for all template engines to be used with\nDjango. Each item of the list is a dictionary containing the options for an\nindividual engine.
\nHere's a setup that tells the Django template engine to load templates from the\ntemplates subdirectory inside each installed application:
TEMPLATES = [\n {\n 'BACKEND': 'django.template.backends.django.DjangoTemplates',\n 'APP_DIRS': True,\n },\n]\nPilihan berikut tersedia untuk semua backend.
\nBACKENDLink to this heading#Awalan: Tidak ditentukan
\nBackend cetakan untuk digunakan. Backend cetakan siap-pakai adalah:
\n'django.template.backends.django.DjangoTemplates'
'django.template.backends.jinja2.Jinja2'
You can use a template backend that doesn't ship with Django by setting\nBACKEND to a fully-qualified path (i.e. 'mypackage.whatever.Backend').
NAMELink to this heading#Awalan: lihat dibawah
\nThe alias for this particular template engine. It's an identifier that allows\nselecting an engine for rendering. Aliases must be unique across all\nconfigured template engines.
\nIt defaults to the name of the module defining the engine class, i.e. the\nnext to last piece of BACKEND, when it isn't\nprovided. For example if the backend is 'mypackage.whatever.Backend' then\nits default name is 'whatever'.
DIRSLink to this heading#Awalan: {} (Daftar kosong)
Direktori-direktori dimana mesih harus dicari untuk berkas-berkas sumber cetakan, dalam urutan pencarian.
\nAPP_DIRSLink to this heading#Awal: False
Apakah mesin harus terlihat untuk berkas sumber cetakan didalam aplikasi terpasang.
\n\nOPTIONSLink to this heading#Awalan: {} (dict kosong)
Extra parameters to pass to the template backend. Available parameters vary\ndepending on the template backend. See\nDjangoTemplates and\nJinja2 for the options of the\nbuilt-in backends.
TEST_RUNNERLink to this heading#Awalan: 'django.test.runner.DiscoverRunner'
Nama dari kelas untuk digunakan untuk memulai antrian percobaan. Lihat Menggunakan kerangka percobaan berbeda.
\nTEST_NON_SERIALIZED_APPSLink to this heading#Awalan: {} (Daftar kosong)
In order to restore the database state between tests for\nTransactionTestCases and database backends without transactions, Django\nwill serialize the contents of all apps\nwhen it starts the test run so it can then reload from that copy before running\ntests that need it.
This slows down the startup time of the test runner; if you have apps that\nyou know don't need this feature, you can add their full names in here (e.g.\n'django.contrib.contenttypes') to exclude them from this serialization\nprocess.
THOUSAND_SEPARATORLink to this heading#Awalan: ',' (Koma)
Default thousand separator used when formatting numbers. This setting is\nused only when USE_THOUSAND_SEPARATOR is True and\nNUMBER_GROUPING is greater than 0.
Note that if USE_L10N is set to True, then the locale-dictated\nformat has higher precedence and will be applied instead.
Lihat juga NUMBER_GROUPING, DECIMAL_SEPARATOR dan USE_THOUSAND_SEPARATOR.
TIME_FORMATLink to this heading#Awalan: 'P' (misalnya 4 p.m.)
The default formatting to use for displaying time fields in any part of the\nsystem. Note that if USE_L10N is set to True, then the\nlocale-dictated format has higher precedence and will be applied instead. See\nallowed date format strings.
Lihat juga DATE_FORMAT dan DATETIME_FORMAT.
TIME_INPUT_FORMATSLink to this heading#Awal:
\n[\n '%H:%M:%S', # '14:30:59'\n '%H:%M:%S.%f', # '14:30:59.000200'\n '%H:%M', # '14:30'\n]\nA list of formats that will be accepted when inputting data on a time field.\nFormats will be tried in order, using the first valid one. Note that these\nformat strings use Python's datetime module syntax, not the format strings from the date\ntemplate filter.
When USE_L10N is True, the locale-dictated format has higher\nprecedence and will be applied instead.
Lihat juga DATE_INPUT_FORMATS dan DATETIME_INPUT_FORMATS.
TIME_ZONELink to this heading#Awalan: 'America/Chicago'
Sebuah string mewakili zona waktu untuk pemasangan ini. Lihat list of time zones.
\n\nNote that this isn't necessarily the time zone of the server. For example, one\nserver may serve multiple Django-powered sites, each with a separate time zone\nsetting.
\nWhen USE_TZ is False, this is the time zone in which Django\nwill store all datetimes. When USE_TZ is True, this is the\ndefault time zone that Django will use to display datetimes in templates and\nto interpret datetimes entered in forms.
On Unix environments (where time.tzset() is implemented), Django sets the\nos.environ['TZ'] variable to the time zone you specify in the\nTIME_ZONE setting. Thus, all your views and models will\nautomatically operate in this time zone. However, Django won't set the TZ\nenvironment variable if you're using the manual configuration option as\ndescribed in manually configuring settings. If Django doesn't set the TZ\nenvironment variable, it's up to you to ensure your processes are running in\nthe correct environment.
USE_DEPRECATED_PYTZLink to this heading#Awal: False
A boolean that specifies whether to use pytz, rather than zoneinfo,\nas the default time zone implementation.
USE_I18NLink to this heading#Awal: True
A boolean that specifies whether Django's translation system should be enabled.\nThis provides a way to turn it off, for performance. If this is set to\nFalse, Django will make some optimizations so as not to load the\ntranslation machinery.
Lihat juga LANGUAGE_CODE, USE_L10N dan USE_TZ.
USE_L10NLink to this heading#Awal: True
A boolean that specifies if localized formatting of data will be enabled by\ndefault or not. If this is set to True, e.g. Django will display numbers and\ndates using the format of the current locale.
Lihat juga LANGUAGE_CODE, USE_I18N dan USE_TZ.
USE_THOUSAND_SEPARATORLink to this heading#Awal: False
A boolean that specifies whether to display numbers using a thousand separator.\nWhen set to True and USE_L10N is also True, Django will\nformat numbers using the NUMBER_GROUPING and\nTHOUSAND_SEPARATOR settings. These settings may also be dictated by\nthe locale, which takes precedence.
Lihat juga DECIMAL_SEPARATOR, NUMBER_GROUPING dan THOUSAND_SEPARATOR.
USE_TZLink to this heading#Awal: False
A boolean that specifies if datetimes will be timezone-aware by default or not.\nIf this is set to True, Django will use timezone-aware datetimes internally.
When USE_TZ is False, Django will use naive datetimes in local time, except\nwhen parsing ISO 8601 formatted strings, where timezone information will always\nbe retained if present.
USE_X_FORWARDED_HOSTLink to this heading#Awal: False
A boolean that specifies whether to use the X-Forwarded-Host header in\npreference to the Host header. This should only be enabled if a proxy\nwhich sets this header is in use.
This setting takes priority over USE_X_FORWARDED_PORT. Per\nRFC 7239 Section 5.3, the X-Forwarded-Host header can include the port\nnumber, in which case you shouldn't use USE_X_FORWARDED_PORT.
USE_X_FORWARDED_PORTLink to this heading#Awal: False
A boolean that specifies whether to use the X-Forwarded-Port header in\npreference to the SERVER_PORT META variable. This should only be\nenabled if a proxy which sets this header is in use.
USE_X_FORWARDED_HOST mengambil prioritas terhadap pengaturan ini.
WSGI_APPLICATIONLink to this heading#Awalan: None
The full Python path of the WSGI application object that Django's built-in\nservers (e.g. runserver) will use. The django-admin\nstartproject management command will create a standard\nwsgi.py file with an application callable in it, and point this setting\nto that application.
If not set, the return value of django.core.wsgi.get_wsgi_application()\nwill be used. In this case, the behavior of runserver will be\nidentical to previous Django versions.
YEAR_MONTH_FORMATLink to this heading#Awalan: 'F Y'
The default formatting to use for date fields on Django admin change-list\npages -- and, possibly, by other parts of the system -- in cases when only the\nyear and month are displayed.
\nFor example, when a Django admin change-list page is being filtered by a date\ndrilldown, the header for a given month displays the month and the year.\nDifferent locales have different formats. For example, U.S. English would say\n"January 2006," whereas another locale might say "2006/January."
\nCatat bahwa jika USE_L10N disetel menjadi True, kemudian bentuk sesuai lokal-yang-ditentukan memiliki hak lebih tinggi dan akan diberlakukan.
Lihat allowed date format strings. Lihat juga DATE_FORMAT, DATETIME_FORMAT, TIME_FORMAT dan MONTH_DAY_FORMAT.
X_FRAME_OPTIONSLink to this heading#Awalan: 'DENY'
Nilai awalan untuk kepala X-Frame-Options digunakan oleh XFrameOptionsMiddleware. Lihat dokumentasi clickjacking protection.
Pengaturan untuk django.contrib.auth.
AUTHENTICATION_BACKENDSLink to this heading#Awalan: ['django.contrib.auth.backends.ModelBackend']
A list of authentication backend classes (as strings) to use when attempting to\nauthenticate a user. See the authentication backends documentation for details.
\nAUTH_USER_MODELLink to this heading#Awalan: 'auth.User'
Model digunakan untuk mewakili User. Lihat Mengganti model User penyesuaian.
\n\nLOGIN_REDIRECT_URLLink to this heading#Awalan: '/accounts/profile/'
The URL or named URL pattern where requests are\nredirected after login when the LoginView\ndoesn't get a next GET parameter.
LOGIN_URLLink to this heading#Awalan: '/accounts/login/'
URL atau named URL pattern dimana permintaan dialihkan untuk masuk ketika menggunakan penghias login_required(), LoginRequiredMixin, atau AccessMixin.
LOGOUT_REDIRECT_URLLink to this heading#Awalan: None
The URL or named URL pattern where requests are\nredirected after logout if LogoutView\ndoesn't have a next_page attribute.
Jika None, pengalihan tidak akan dilakukan dan tampilan keluar akan dibangun.
PASSWORD_RESET_TIMEOUTLink to this heading#Awalan: 259200 (3 hari, dalam detik)
Jumlah detik dari tautan setel kembali sandi yang sah.
\nDigunakan oleh PasswordResetConfirmView.
PASSWORD_HASHERSLink to this heading#Lihat Bagaimana Django menyimpan sandi.
\nAwal:
\n[\n 'django.contrib.auth.hashers.PBKDF2PasswordHasher',\n 'django.contrib.auth.hashers.PBKDF2SHA1PasswordHasher',\n 'django.contrib.auth.hashers.Argon2PasswordHasher',\n 'django.contrib.auth.hashers.BCryptSHA256PasswordHasher',\n]\nAUTH_PASSWORD_VALIDATORSLink to this heading#Awalan: {} (Daftar kosong)
The list of validators that are used to check the strength of user's passwords.\nSee Pengesahan sandi for more details. By default, no validation is\nperformed and all passwords are accepted.
\nPengaturan django.contrib.messages.
MESSAGE_LEVELLink to this heading#Awalan: messages.INFO
Setel tingkatan pesan minimal yang akan direkam oleh kerangka kerja pesan. Lihat message levels untuk rincian lebih.
\n\nMESSAGE_STORAGELink to this heading#Awalan: 'django.contrib.messages.storage.fallback.FallbackStorage'
Mengendalikan dimana Django menyimpan data pesan. Nilai sah adalah:
\n'django.contrib.messages.storage.fallback.FallbackStorage'
'django.contrib.messages.storage.session.SessionStorage'
'django.contrib.messages.storage.cookie.CookieStorage'
Lihat message storage backends untuk lebih rinci.
\nBackend yang menggunakan kue -- CookieStorage dan FallbackStorage -- menggunakan nilai dari SESSION_COOKIE_DOMAIN, SESSION_COOKIE_SECURE dan SESSION_COOKIE_HTTPONLY ketika menyetel kue mereka.
Pengaturan untuk django.contrib.sessions.
SESSION_CACHE_ALIASLink to this heading#Awalan: 'default'
Jika anda sedang menggunakan cache-based session storage, ini memilih cache untuk digunakan.
\nSESSION_ENGINELink to this heading#Awalan: 'django.contrib.sessions.backends.db'
Mengendalikan dimana Django menyimpan data sesi. Mesin yang disertakan adalah:
\n'django.contrib.sessions.backends.db'
'django.contrib.sessions.backends.file'
'django.contrib.sessions.backends.cache'
'django.contrib.sessions.backends.cached_db'
'django.contrib.sessions.backends.signed_cookies'
Lihat Konfigurasi mesin sesi untuk rincian lebih.
\nSESSION_EXPIRE_AT_BROWSER_CLOSELink to this heading#Awal: False
Whether to expire the session when the user closes their browser. See\nBrowser-length sessions vs. persistent sessions.
\nSESSION_FILE_PATHLink to this heading#Awalan: None
If you're using file-based session storage, this sets the directory in\nwhich Django will store session data. When the default value (None) is\nused, Django will use the standard temporary directory for the system.
SESSION_SAVE_EVERY_REQUESTLink to this heading#Awal: False
Whether to save the session data on every request. If this is False\n(default), then the session data will only be saved if it has been modified --\nthat is, if any of its dictionary values have been assigned or deleted. Empty\nsessions won't be created, even if this setting is active.
SESSION_SERIALIZERLink to this heading#Awalan: 'django.contrib.sessions.serializers.JSONSerializer'
Full import path of a serializer class to use for serializing session data.\nIncluded serializers are:
\n'django.contrib.sessions.serializers.PickleSerializer'
'django.contrib.sessions.serializers.JSONSerializer'
See Serialisasi sesi for details, including a warning regarding\npossible remote code execution when using\nPickleSerializer.
Pengaturan untuk django.contrib.sites.
SITE_IDLink to this heading#Awalan: Tidak ditentukan
\nThe ID, as an integer, of the current site in the django_site database\ntable. This is used so that application data can hook into specific sites\nand a single database can manage content for multiple sites.
Pengaturan untuk django.contrib.staticfiles.
STATIC_ROOTLink to this heading#Awalan: None
Jalur mutlak ke direktori dimana collectstatic akan mengumpulkan berkas-berkas tetap untuk pengembangan.
Contoh: "/var/www/example.com/static/"
If the staticfiles contrib app is enabled\n(as in the default project template), the collectstatic management\ncommand will collect static files into this directory. See the how-to on\nmanaging static files for more details about\nusage.
STATIC_URLLink to this heading#Awalan: None
URL digunakan ketika mengacu ke berkas-berkas tetap bertempat dalam STATIC_ROOT.
Example: "static/" or "http://static.example.com/"
Jika bukan None, ini akan digunakan sebagai jalur dasar untuk asset definitions (kelas Media) dan staticfiles app.
Itu harus berakhir dalam sebuah garis miring jika disetel ke nilai bukan-kosong.
\nAnda mungkin butuh untuk configure these files to be served in development dan akan sangat perlu melakukan itu in production.
\n\nSTATICFILES_DIRSLink to this heading#Awalan: {} (Daftar kosong)
This setting defines the additional locations the staticfiles app will traverse\nif the FileSystemFinder finder is enabled, e.g. if you use the\ncollectstatic or findstatic management command or use the\nstatic file serving view.
Ini harus berupa kumpulan dari daftar string yang mengandung jalur penuh ke berkas-berkas tambahan anda misalnya:
\nSTATICFILES_DIRS = [\n "/home/special.polls.com/polls/static",\n "/home/polls.com/polls/static",\n "/opt/webfiles/common",\n]\nCatat bahwa jalur-jalur ini harus menggunakan garis miring depan gaya-Unix, bahkan pada Windows (misalnya "C:/Users/user/mysite/extra_static_content").
Dalam kasus anda ingin mengacu pada berkas-berkas dalam satu dari tempat-tempat dengan namespace tambahan, anda dapat pilihan menyediakan awalan sebagai tuple-tuple (prefix, path), misalnya:
STATICFILES_DIRS = [\n # ...\n ("downloads", "/opt/webfiles/stats"),\n]\nFor example, assuming you have STATIC_URL set to 'static/', the\ncollectstatic management command would collect the "stats" files\nin a 'downloads' subdirectory of STATIC_ROOT.
Ini akan mengizinkan anda mengacu ke berkasl lokal '/opt/webfiles/stats/polls_20101022.tar.gz' dengan '/static/downloads/polls_20101022.tar.gz' dalam cetakan anda, misalnya:
<a href="{% static 'downloads/polls_20101022.tar.gz' %}">\nSTATICFILES_STORAGELink to this heading#Awalan: 'django.contrib.staticfiles.storage.StaticFilesStorage'
Mesin penyimpanan berkas digunakan ketika mengumpulkan berkas-berkas statis dengan perintah pengelolaan collectstatic.
Sebauh contoh siap-pakai dari backend penyimpanan ditentukan dalam pengaturan ini dapat ditemukan pada django.contrib.staticfiles.storage.staticfiles_storage.
Sebagai sebuah contoh, lihat Melayani berkas statis dari layanan cloud atau CDN.
\nSTATICFILES_FINDERSLink to this heading#Awal:
\n[\n 'django.contrib.staticfiles.finders.FileSystemFinder',\n 'django.contrib.staticfiles.finders.AppDirectoriesFinder',\n]\nDaftar dari penemu backend yang mengetahui bagaimana menemukan berkas-berkas statis dalam beragam tempat.
\nThe default will find files stored in the STATICFILES_DIRS setting\n(using django.contrib.staticfiles.finders.FileSystemFinder) and in a\nstatic subdirectory of each app (using\ndjango.contrib.staticfiles.finders.AppDirectoriesFinder). If multiple\nfiles with the same name are present, the first file that is found will be\nused.
One finder is disabled by default:\ndjango.contrib.staticfiles.finders.DefaultStorageFinder. If added to\nyour STATICFILES_FINDERS setting, it will look for static files in\nthe default file storage as defined by the DEFAULT_FILE_STORAGE\nsetting.
Penemu berkas statis saat ini dianggap antarmuka pribadi, dan antarmuka ini dengan demikian tidak terdokumentasi.
\ni18n/l10n)Link to this heading#Keamanan
\n\nCross Site Request Forgery Protection
\n\nBasisdata: TEST