django-admin dan manage.pyLink to this heading#django-admin adalah kegunaan baris-perintah Django utnuk tugas-tugas administratif. Dokumen ini ringkasa semua itu dapat lakukan.
In addition, manage.py is automatically created in each Django project. It\ndoes the same thing as django-admin but also sets the\nDJANGO_SETTINGS_MODULE environment variable so that it points to your\nproject's settings.py file.
The django-admin script should be on your system path if you installed\nDjango via pip. If it's not in your path, ensure you have your virtual\nenvironment activated.
Umumnya, ketika bekerja pada proyek Django tunggal, itu lebih mudah menggunakan manage.py daripada django-admin. Jika anda butuh mengganti diantara banyak berkas-berkas pengaturan Django, gunakan django-admin dengan pilihan baris perintah DJANGO_SETTINGS_MODULE atau --settings.
Contoh-contoh baris-perintah sepanjang dokumen ini menggunakan django-admin untuk menjadi konsisten, tetapi contoh apapun dapat menggunakan manage.py atau python -m django juga.
Linux / macOS
$ django-admin <command> [options]\n$ manage.py <command> [options]\n$ python -m django <command> [options]\nWindows
...\\> django-admin <command> [options]\n...\\> manage.py <command> [options]\n...\\> py -m django <command> [options]\ncommand harys berupa satu dari perintah terdaftar dalam dokumen ini. options, yaitu pilihan, harus berupa nol atau lebih dari pilihan tersedia untuk perintah yang diberikan.
Menjalankan django-admin help untuk menampilkan informasi penggunaan dan daftar dari perintah disediakan oleh setiap aplikasi.
Jalankan django-admin help --commands untuk menampilkan daftar dari perintah tersedia.
Menjalankan django-admin help <command> untuk menampilkan gambaran dari perintah yang diberikan dan daftar dari pilihan yang tersedia.
Banyak perintah mengambil daftar dari "app names." Sebuah "app name" adalah nama dasar dari paket mengandung model-model anda. Sebagai contoh, jika INSTALLED_APPS anda mengandung string 'mysite.blog', nama aplikasi adalah blog.
Jalankan django-admin version untuk menjalankan versi Django saat ini.
Keluaran mengikuti skema digambarkan dalam PEP 440:
\n1.4.dev17026\n1.4a1\n1.4\nUse --verbosity, where it is supported, to specify the amount of\nnotification and debug information that django-admin prints to the console.
checkLink to this heading#Menggunakan system check framework untuk memeriksa keseluruhan proyek Django untuk masalah-masalah umum.
\nSecara awalan, semua aplikasi akan diperiksa. Anda dapat memeriksa bagian dari aplikasi dengan menyediakan daftar dari label-label aplikasi sebagai argumen:
\ndjango-admin check auth admin myapp\nKerangka sistem pemeriksaan melakukan banyak jenis-jenis berbeda dari pemeriksaan yang categorized with tags. Anda dapat menggunakan etiket-etiket ini untuk membatasi pemeriksaan dilakukan untuk hanya di kategori tertentu. Sebagai contoh, untuk hanya melakukan pemeriksaan model dan kesesuaian, jalankan:
\ndjango-admin check --tag models --tag compatibility\nSpecifies the database to run checks requiring database access:
\ndjango-admin check --database default --database other\nBy default, these checks will not be run.
\nDaftarkan semua etiket tersedia.
\nMengaktifkan beberapa pemeriksaan tambahan yang hanya bersangkutan dalam pengaturan pengembangan.
\nYou can use this option in your local development environment, but since your\nlocal development settings module may not have many of your production settings,\nyou will probably want to point the check command at a different settings\nmodule, either by setting the DJANGO_SETTINGS_MODULE environment\nvariable, or by passing the --settings option:
django-admin check --deploy --settings=production_settings\nAtau anda dapat menjalankan itu langsung pada produksi atau tahap pengembangan untuk memeriksa bahwa pengaturan benar adalah digunakan (menghilangkan --settings). Anda bahkan dapat membuat itu bagian dari deretan percobaan kesatuan anda.
Menentukan tingkat pesan yang akan menyebabkan perintah keluar dengan keadaan bukan-nol. Awalan adalah ERROR.
compilemessagesLink to this heading#Menyusun berkas-berkas .po dibuat oleh makemessages untuk berkas-berkas .mo untuk digunakan dengan dukungan gettext siap-pakai. Lihat Internasionalisasi dan lokalisasi.
Menentukan lokal-loka untuk diolah. Jika tidak disediakan, semua lokal-lokal adalah terolah.
\nMenentukan lokal untuk tidak menyertakan dari pengolahan. jika tidak disediakan, tidak ada lokal tidak disertakan.
\nIncludes fuzzy translations into compiled files.
\nContoh penggunaan:
\ndjango-admin compilemessages --locale=pt_BR\ndjango-admin compilemessages --locale=pt_BR --locale=fr -f\ndjango-admin compilemessages -l pt_BR\ndjango-admin compilemessages -l pt_BR -l fr --use-fuzzy\ndjango-admin compilemessages --exclude=pt_BR\ndjango-admin compilemessages --exclude=pt_BR --exclude=fr\ndjango-admin compilemessages -x pt_BR\ndjango-admin compilemessages -x pt_BR -x fr\nIgnores directories matching the given glob-style pattern. Use\nmultiple times to ignore more.
Contoh penggunaan:
\ndjango-admin compilemessages --ignore=cache --ignore=outdated/*/locale\ncreatecachetableLink to this heading#Membuat tabel-tabel penyimpanan sementara untuk digunakan dengan backend penyimpanan sementara basisdata menggunakan informasi dari berkas pengaturan anda. Lihat Kerangka kerja penyimpanan Django untuk informasi lebih.
\nMenentukan basisdata dimana tabel-tabel penyimpanan sementara akan dibuat. Awalan pada default.
Mencetak SQL yang akan dijalankan tanpa sebenarnya menjalankan itu, sehingga anda dapat menyesuaikan itu atau menggunakan kerangka kerja perpindahan.
\ndbshellLink to this heading#Jalankan baris-perintah klien untuk mesin basisdata ditentukan dalam pengaturan ENGINE anda, dengan parameter penghubung USER, PASSWORD, dll., dilakukan dalam pengaturan anda.
Untuk PostgreSQL, ini menjalankan klien baris-perintah psql.
Untuk MySQL, ini menjalankan klien baris-perintah mysql.
Untuk SQLite, ini menjalankan klien baris-perintah sqlite3.
Untuk Oracle, ini menjalankan klien baris-perintah sqlplus.
This command assumes the programs are on your PATH so that a call to\nthe program name (psql, mysql, sqlite3, sqlplus) will find the\nprogram in the right place. There's no way to specify the location of the\nprogram manually.
Menentukan basisdalam kedalam dimana membuka sebuah cangkang. Awalan pada default.
Any arguments following a -- divider will be passed on to the underlying\ncommand-line client. For example, with PostgreSQL you can use the psql\ncommand's -c flag to execute a raw SQL query directly:
Linux / macOS
$ django-admin dbshell -- -c 'select current_user'\n current_user\n--------------\n postgres\n(1 row)\nWindows
...\\> django-admin dbshell -- -c 'select current_user'\n current_user\n--------------\n postgres\n(1 row)\nOn MySQL/MariaDB, you can do this with the mysql command's -e flag:
Linux / macOS
$ django-admin dbshell -- -e "select user()"\n+----------------------+\n| user() |\n+----------------------+\n| djangonaut@localhost |\n+----------------------+\nWindows
...\\> django-admin dbshell -- -e "select user()"\n+----------------------+\n| user() |\n+----------------------+\n| djangonaut@localhost |\n+----------------------+\ndiffsettingsLink to this heading#Menampilkan perbedaan diantara berkas pengaturan saat ini dan pengaturan awalan Django (atau berkas pengaturan lain ditentukan oleh --default).
Pengaturan yang tidak muncul dalam awalan diikuti oleh "###". Sebagai contoh, pengaturan awalan tidak menentukan ROOT_URLCONF, jadi ROOT_URLCONF diikuti oleh "###" dalam keluaran dari diffsettings.
Menampilkan semua pengaturan, bahkan jika mereka memiliki nilai awalan Django. Pengaturan seperti itu diawali oleh "###".
Modul pengaturan untuk membandingkan terhadap pengaturan saat ini. Biarkan kosong untuk membandingkan terhadap pengaturan awalan Django.
\nMenentukan bentuk keluaran. Nilai-nilai tersedia adalah hash dan unified. hash adalah suasana awalan yang menampilkan keluaran yang digambarkan diatas. unified menampilkan keluaran mirip pada diff -u. Pengaturan awalan diawali dengan tanda kurang, diikuti dengan merubah pengaturan diawali dengan sebuah tanda tambah.
dumpdataLink to this heading#Keluaran pada standar pengeluaran semua data dalam basisdata terkait dengan aplikasi bernama.
\nJika tidak ada nama aplikasi disediakan, semua aplikasi terpasang akan dibuang.
\nKeluaran dari dumpdata dapat digunakan sebagai masukan untuk loaddata.
Note that dumpdata uses the default manager on the model for selecting the\nrecords to dump. If you're using a custom manager as\nthe default manager and it filters some of the available records, not all of the\nobjects will be dumped.
Menggunakan pengelola dasar Django, membuang rekaman yang mungkin sebaliknya disaring atau dirubah oleh pengelola penyesuaian.
\nMenentukan bentuk serialisasi dari keluaran. Awalan pada JSON. Bentuk-bentuk didukung didaftarkan dalam Bentuk-bentuk serialisasi.
\nMenentukan angka dari lekukan ruang untuk digunakan dalam keluaran. Awalan pada None yang menampilkan semua data dalam baris tunggal.
Prevents specific applications or models (specified in the form of\napp_label.ModelName) from being dumped. If you specify a model name, then\nonly that model will be excluded, rather than the entire application. You can\nalso mix application names and model names.
JIka anda ingin tidak menyertakan banyak aplikasi, lewatkan --exclude lebih dari sekali:
django-admin dumpdata --exclude=auth --exclude=contenttypes\nMenentukan basisdata dari data mana akan dibuang. Awalan pada default.
Uses the natural_key() model method to serialize any foreign key and\nmany-to-many relationship to objects of the type that defines the method. If\nyou're dumping contrib.auth Permission objects or\ncontrib.contenttypes ContentType objects, you should probably use this\nflag. See the natural keys\ndocumentation for more details on this and the next option.
Menghilangkan primary key dalam penserialan data dari obyek ini sejak itu dapat dihitung selama pendeserialisasi.
\nOutputs only the objects specified by a comma separated list of primary keys.\nThis is only available when dumping one model. By default, all the records of\nthe model are output.
\nMenentukan sebuah berkas untuk menulis data terserialisasi. Secara awalan, data pergi ke keluaran standar.
\nKetika pilihan ini disetel dan --verbosity lebih besar dari 0 (awalan), sebuah batang kemajuan ditampilkan dalam terminal.
The output file can be compressed with one of the bz2, gz, lzma, or\nxz formats by ending the filename with the corresponding extension.\nFor example, to output the data as a compressed JSON file:
django-admin dumpdata -o mydata.json.gz\nflushLink to this heading#Removes all data from the database and re-executes any post-synchronization\nhandlers. The table of which migrations have been applied is not cleared.
\nIf you would rather start from an empty database and rerun all migrations, you\nshould drop and recreate the database and then run migrate instead.
Menekan semua permintaan pengguna.
\nMenentukan basisdata untuk dialirkan. Awalan pada default.
inspectdbLink to this heading#Introspects the database tables in the database pointed-to by the\nNAME setting and outputs a Django model module (a models.py\nfile) to standard output.
You may choose what tables or views to inspect by passing their names as\narguments. If no arguments are provided, models are created for views only if\nthe --include-views option is used. Models for partition tables are\ncreated on PostgreSQL if the --include-partitions option is used.
Gunakan ini jika anda mempunyai sebuah basisdata warisan dengan dimana anda akan menggunakan Django. Tulisan akan will memeriksa basisdata dan membuat sebuah model untuk setiap tabel dalam itu.
\nAs you might expect, the created models will have an attribute for every field\nin the table. Note that inspectdb has a few special cases in its field-name\noutput:
If inspectdb cannot map a column's type to a model field type, it'll\nuse TextField and will insert the Python comment\n'This field type is a guess.' next to the field in the generated\nmodel. The recognized fields may depend on apps listed in\nINSTALLED_APPS. For example, django.contrib.postgres adds\nrecognition for several PostgreSQL-specific field types.
If the database column name is a Python reserved word (such as\n'pass', 'class' or 'for'), inspectdb will append\n'_field' to the attribute name. For example, if a table has a column\n'for', the generated model will have a field 'for_field', with\nthe db_column attribute set to 'for'. inspectdb will insert\nthe Python comment\n'Field renamed because it was a Python reserved word.' next to the\nfield.
This feature is meant as a shortcut, not as definitive model generation. After\nyou run it, you'll want to look over the generated models yourself to make\ncustomizations. In particular, you'll need to rearrange models' order, so that\nmodels that refer to other models are ordered properly.
\nDjango doesn't create database defaults when a\ndefault is specified on a model field.\nSimilarly, database defaults aren't translated to model field defaults or\ndetected in any fashion by inspectdb.
By default, inspectdb creates unmanaged models. That is, managed = False\nin the model's Meta class tells Django not to manage each table's creation,\nmodification, and deletion. If you do want to allow Django to manage the\ntable's lifecycle, you'll need to change the\nmanaged option to True (or remove\nit because True is its default value).
Model-model dibuat untuk mewujudkan tampilan jika --include-views digunakan.
Model-model dibuat untuk tabel-tabel asing.
Model-model dibuat untuk mewujudkan tampilan jika --include-views digunakan.
Model dibuat untuk penyekatan tabel jika --include-partitions digunakan.
Menentukan basisdata untuk mawas diri. Awalan pada default.
Jika pilihan ini disediakan, model juga dibuat untuk penyekatan.
\nHanya mendukung untuk PostgreSQL dijalankan.
\nJika pilihan ini disediakan, model juga dibuat untuk tampilan basisdata.
\nloaddataLink to this heading#Searches for and loads the contents of the named fixture into the database.
\nMenentukan basisdata dimana data akan dimuat. Awalan pada default.
Ignores fields and models that may have been removed since the fixture was\noriginally generated.
\nSpecifies a single app to look for fixtures in rather than looking in all apps.
\nMenentukan serialization format (misalnya, json atau xml) untuk fixture read from stdin.
Excludes loading the fixtures from the given applications and/or models (in the\nform of app_label or app_label.ModelName). Use the option multiple\ntimes to exclude more than one app or model.
A fixture is a collection of files that contain the serialized contents of\nthe database. Each fixture has a unique name, and the files that comprise the\nfixture can be distributed over multiple directories, in multiple applications.
\nDjango akan mencari dalam tiga lokasi untuk fixture:
\nDalam direktori fixture dari setiap aplikasi terpasang
Dalam direktori apapun bernama dalalam pengaturan FIXTURE_DIRS.
In the literal path named by the fixture
Django will load any and all fixtures it finds in these locations that match\nthe provided fixture names.
\nIf the named fixture has a file extension, only fixtures of that type\nwill be loaded. For example:
\ndjango-admin loaddata mydata.json\nwould only load JSON fixtures called mydata. The fixture extension\nmust correspond to the registered name of a\nserializer (e.g., json or xml).
If you omit the extensions, Django will search all available fixture types\nfor a matching fixture. For example:
\ndjango-admin loaddata mydata\nwould look for any fixture of any fixture type called mydata. If a fixture\ndirectory contained mydata.json, that fixture would be loaded\nas a JSON fixture.
The fixtures that are named can include directory components. These\ndirectories will be included in the search path. For example:
\ndjango-admin loaddata foo/bar/mydata.json\nakan mencari <app_label>/fixtures/foo/bar/mydata.json untuk setiap aplikasi terpasang, <dirname>/foo/bar/mydata.json untuk setiap direktori dalam FIXTURE_DIRS, dan jalur harfiah foo/bar/mydata.json.
When fixture files are processed, the data is saved to the database as is.\nModel defined save() methods are not called, and\nany pre_save or\npost_save signals will be called with\nraw=True since the instance only contains attributes that are local to the\nmodel. You may, for example, want to disable handlers that access\nrelated fields that aren't present during fixture loading and would otherwise\nraise an exception:
from django.db.models.signals import post_save\nfrom .models import MyModel\n\ndef my_handler(**kwargs):\n # disable the handler during fixture loading\n if kwargs['raw']:\n return\n ...\n\npost_save.connect(my_handler, sender=MyModel)\nYou could also write a decorator to encapsulate this logic:
\nfrom functools import wraps\n\ndef disable_for_loaddata(signal_handler):\n """\n Decorator that turns off signal handlers when loading fixture data.\n """\n @wraps(signal_handler)\n def wrapper(*args, **kwargs):\n if kwargs['raw']:\n return\n signal_handler(*args, **kwargs)\n return wrapper\n\n@disable_for_loaddata\ndef my_handler(**kwargs):\n ...\nJust be aware that this logic will disable the signals whenever fixtures are\ndeserialized, not just during loaddata.
Note that the order in which fixture files are processed is undefined. However,\nall fixture data is installed as a single transaction, so data in\none fixture can reference data in another fixture. If the database backend\nsupports row-level constraints, these constraints will be checked at the\nend of the transaction.
\nPerintah dumpdata dapat digunakan untuk membangkitkan masukan untuk loaddata.
Fixtures may be compressed in zip, gz, bz2, lzma, or xz\nformat. For example:
django-admin loaddata mydata.json\nwould look for any of mydata.json, mydata.json.zip, mydata.json.gz,\nmydata.json.bz2, mydata.json.lzma, or mydata.json.xz. The first\nfile contained within a compressed archive is used.
Note that if two fixtures with the same name but different\nfixture type are discovered (for example, if mydata.json and\nmydata.xml.gz were found in the same fixture directory), fixture\ninstallation will be aborted, and any data installed in the call to\nloaddata will be removed from the database.
If you're in a multi-database setup, you might have fixture data that\nyou want to load onto one database, but not onto another. In this\nsituation, you can add a database identifier into the names of your fixtures.
\nFor example, if your DATABASES setting has a 'users' database\ndefined, name the fixture mydata.users.json or\nmydata.users.json.gz and the fixture will only be loaded when you\nspecify you want to load data into the users database.
stdinLink to this heading#You can use a dash as the fixture name to load input from sys.stdin. For\nexample:
django-admin loaddata --format=json -\nWhen reading from stdin, the --format option\nis required to specify the serialization format\nof the input (e.g., json or xml).
Loading from stdin is useful with standard input and output redirections.\nFor example:
django-admin dumpdata --format=json --database=test app_label.ModelName | django-admin loaddata --format=json --database=prod -\nmakemessagesLink to this heading#Runs over the entire source tree of the current directory and pulls out all\nstrings marked for translation. It creates (or updates) a message file in the\nconf/locale (in the Django tree) or locale (for project and application)\ndirectory. After making changes to the messages files you need to compile them\nwith compilemessages for use with the builtin gettext support. See\nthe i18n documentation for details.
This command doesn't require configured settings. However, when settings aren't\nconfigured, the command can't ignore the MEDIA_ROOT and\nSTATIC_ROOT directories or include LOCALE_PATHS.
Perbaharui berkas pesan untuk semua bahasa tersedia.
\nMenentukan daftar ekstensi berkas untuk diuji (awalan: html, txt, py atau js jika --domain adalah js).
Contoh penggunaan:
\ndjango-admin makemessages --locale=de --extension xhtml\nPisahkan banyak ekstensi dengan koma atau menggunakan -e atau --extension berulang kali:
django-admin makemessages --locale=de --extension=html,txt --extension xml\nMenentukan lokal untuk diolah.
\nMenentukan lokal untuk tidak menyertakan dari pengolahan. jika tidak disediakan, tidak ada lokal tidak disertakan.
\nContoh penggunaan:
\ndjango-admin makemessages --locale=pt_BR\ndjango-admin makemessages --locale=pt_BR --locale=fr\ndjango-admin makemessages -l pt_BR\ndjango-admin makemessages -l pt_BR -l fr\ndjango-admin makemessages --exclude=pt_BR\ndjango-admin makemessages --exclude=pt_BR --exclude=fr\ndjango-admin makemessages -x pt_BR\ndjango-admin makemessages -x pt_BR -x fr\nMenentukan ranah dari berkas pesan. Pilihan didukung adalah:
\nBerkas-berkas django for all *.py, *.html and ``*.txt``(awal)
djangojs untuk berkas-berkas *.js
Follows symlinks to directories when looking for new translation strings.
\nContoh penggunaan:
\ndjango-admin makemessages --locale=de --symlinks\nIgnores files or directories matching the given glob-style pattern. Use\nmultiple times to ignore more.
Pola ini digunakan secara awalan: 'CVS', '.*', '*~', '*.pyc'.
Contoh penggunaan:
\ndjango-admin makemessages --locale=en_US --ignore=apps/* --ignore=secret/*.html\nMeniadakan nilai awalan dari --ignore.
Disables breaking long message lines into several lines in language files.
\nSuppresses writing '#: filename:line’ comment lines in language files.\nUsing this option makes it harder for technically skilled translators to\nunderstand each message's context.
Controls #: filename:line comment lines in language files. If the option\nis:
full (the default if not given): the lines include both file name and\nline number.
file: nomor baris dihilangkan.
never: baris-baris ditekan (sama seperti --no-location).
Dibtuhkan gettext 0.19 atau terbaru.
Prevents deleting the temporary .pot files generated before creating the\n.po file. This is useful for debugging errors which may prevent the final\nlanguage files from being created.
makemigrationsLink to this heading#Creates new migrations based on the changes detected to your models.\nMigrations, their relationship with apps and more are covered in depth in\nthe migrations documentation.
\nProviding one or more app names as arguments will limit the migrations created\nto the app(s) specified and any dependencies needed (the table at the other end\nof a ForeignKey, for example).
To add migrations to an app that doesn't have a migrations directory, run\nmakemigrations with the app's app_label.
Suppresses all user prompts. If a suppressed prompt cannot be resolved\nautomatically, the command will exit with error code 3.
\nOutputs an empty migration for the specified apps, for manual editing. This is\nfor advanced users and should not be used unless you are familiar with the\nmigration format, migration operations, and the dependencies between your\nmigrations.
\nShows what migrations would be made without actually writing any migrations\nfiles to disk. Using this option along with --verbosity 3 will also show\nthe complete migrations files that would be written.
Mengadakan perbaikan dari pertentangan perpindahan.
\nAllows naming the generated migration(s) instead of using a generated name. The\nname must be a valid Python identifier.
\nMembangkitkan berkas-berkas perpindahan tanpa versi Django dan kepala timestamp.
\nMakes makemigrations exit with a non-zero status when model changes without\nmigrations are detected.
Diverts log output and input prompts to stderr, writing only paths of\ngenerated migration files to stdout.
migrateLink to this heading#Synchronizes the database state with the current set of models and migrations.\nMigrations, their relationship with apps and more are covered in depth in\nthe migrations documentation.
\nKebiasaan dari perintah ini berubah tergantung pada argumen disediakan:
\nTidak ada argumen: Semua aplikasi mempunyai semua perpindahan mereka berjalan.
<app_label>: The specified app has its migrations run, up to the most\nrecent migration. This may involve running other apps' migrations too, due\nto dependencies.
<app_label> <migrationname>: Brings the database schema to a state where\nthe named migration is applied, but no later migrations in the same app are\napplied. This may involve unapplying migrations if you have previously\nmigrated past the named migration. You can use a prefix of the migration\nname, e.g. 0001, as long as it's unique for the given app name. Use the\nname zero to migrate all the way back i.e. to revert all applied\nmigrations for an app.
Menentukan basisdata untuk perpindahan. Awal ke default.
Marks the migrations up to the target one (following the rules above) as\napplied, but without actually running the SQL to change your database schema.
\nThis is intended for advanced users to manipulate the\ncurrent migration state directly if they're manually applying changes;\nbe warned that using --fake runs the risk of putting the migration state\ntable into a state where manual recovery will be needed to make migrations\nrun correctly.
Mengizinkan Django melewti perpindahan inisial applikasi jika semua tabel basisdata dengan nama-nama dari semua model dibuat oleh semua tindakan CreateModel dalam perpindahan itu yang sudah ada. Pilihan ini diperntukkan penggunaan ketika perpindahan penjalanan pertama terhadap basisdata yang sudah ada sebelumnya menggunakan perpindahan. Pilihan ini bukan, bagaimanapun, diperiksa untuk pencocokan skema basisdata diluar pencocokan nama-nama tabel dan sehinggaa hanya aman digunakan jika anda percaya diri bahwa skema yang ada cocok apa yang direkam dalam perpindahan inisial anda.
Shows the migration operations that will be performed for the given migrate\ncommand.
Allows creating tables for apps without migrations. While this isn't\nrecommended, the migrations framework is sometimes too slow on large projects\nwith hundreds of models.
\nSuppresses all user prompts. An example prompt is asking about removing stale\ncontent types.
\nMakes migrate exit with a non-zero status when unapplied migrations are\ndetected.
Deletes nonexistent migrations from the django_migrations table. This is\nuseful when migration files replaced by a squashed migration have been removed.\nSee Squashing migrations for more details.
optimizemigrationLink to this heading#Optimizes the operations for the named migration and overrides the existing\nfile. If the migration contains functions that must be manually copied, the\ncommand creates a new migration file suffixed with _optimized that is meant\nto replace the named migration.
Makes optimizemigration exit with a non-zero status when a migration can be\noptimized.
runserverLink to this heading#Starts a lightweight development web server on the local machine. By default,\nthe server runs on port 8000 on the IP address 127.0.0.1. You can pass in an\nIP address and port number explicitly.
If you run this script as a user with normal privileges (recommended), you\nmight not have access to start a port on a low port number. Low port numbers\nare reserved for the superuser (root).
\nPeladen ini menggunakan obyek aplikasi WSGI ditentukan oleh pengaturan WSGI_APPLICATION.
DO NOT USE THIS SERVER IN A PRODUCTION SETTING. It has not gone through\nsecurity audits or performance tests. (And that's how it's gonna stay. We're in\nthe business of making web frameworks, not web servers, so improving this\nserver to be able to handle a production environment is outside the scope of\nDjango.)
\nThe development server automatically reloads Python code for each request, as\nneeded. You don't need to restart the server for code changes to take effect.\nHowever, some actions like adding files don't trigger a restart, so you'll\nhave to restart the server in these cases.
\nIf you're using Linux or MacOS and install both pywatchman and the\nWatchman service, kernel signals will be used to autoreload the server\n(rather than polling file modification timestamps each second). This offers\nbetter performance on large projects, reduced response time after code changes,\nmore robust change detection, and a reduction in power usage. Django supports\npywatchman 1.2.0 and higher.
When you start the server, and each time you change Python code while the\nserver is running, the system check framework will check your entire Django\nproject for some common errors (see the check command). If any\nerrors are found, they will be printed to standard output. You can use the\n--skip-checks option to skip running system checks.
You can run as many concurrent servers as you want, as long as they're on\nseparate ports by executing django-admin runserver more than once.
Note that the default IP address, 127.0.0.1, is not accessible from other\nmachines on your network. To make your development server viewable to other\nmachines on the network, use its own IP address (e.g. 192.168.2.1), 0\n(shortcut for 0.0.0.0), 0.0.0.0, or :: (with IPv6 enabled).
Anda dapat menyediakan sebuah alamat IPv6 dikelilingi oleh tanda kurung (misalnya [200a::1]:8000). Ini akan otomatis mengadakan dukungan IPv6.
Sebuah nama rumah mengandung karakter hanya-ASCII dapat juga digunakan.
\nJika staticfiles aplikasi bantuan diadakan (awalan dalam proyek baru) perintah runserver akan ditimpa dengan perintah runserver nya sendiri.
Logging of each request and response of the server is sent to the\ndjango.server logger.
\nDisables the auto-reloader. This means any Python code changes you make while\nthe server is running will not take effect if the particular Python modules\nhave already been loaded into memory.
\nDisables use of threading in the development server. The server is\nmultithreaded by default.
\nMenggunakan IPv6 untuk peladen pengembangan. Ini merubah alamat IP awal dari 127.0.0.1 ke ::1.
Port 8000 pada alamat IP 127.0.0.1:
django-admin runserver\nPort 8000 pada alamat IP 1.2.3.4:
django-admin runserver 1.2.3.4:8000\nPort 7000 pada alamat IP 127.0.0.1:
django-admin runserver 7000\nPort 7000 pada alamat IP 1.2.3.4:
django-admin runserver 1.2.3.4:7000\nPort 8000 pada alamat IPv6 ::1:
django-admin runserver -6\nPort 7000 pada alamat IPv6 ::1:
django-admin runserver -6 7000\nPort 7000 pada alamat IPv6 2001:0db8:1234:5678::9:
django-admin runserver [2001:0db8:1234:5678::9]:7000\nPort 8000 pada alamat IPv4 dari rumah localhost:
django-admin runserver localhost:8000\nPort 8000 pada alamat IPv6 dari rumah localhost:
django-admin runserver -6 localhost:8000\nBy default, the development server doesn't serve any static files for your site\n(such as CSS files, images, things under MEDIA_URL and so forth). If\nyou want to configure Django to serve static media, read\nHow to manage static files (e.g. images, JavaScript, CSS).
sendtestemailLink to this heading#Kirim surel percobaan (untuk menegaskan surel mengirim melalui Django bekerja) ke penerima ditentukan. Sebagai contoh:
\ndjango-admin sendtestemail foo@example.com bar@example.com\nAda sepasang pilihan, dan anda mungkin menggunakan perpaduan apapun dari mereka bersama-sama:
\nMails the email addresses specified in MANAGERS using\nmail_managers().
Menyuarti alamat surel ditentukan dalam ADMINS menggunakan mail_admins().
sendtestemailLink to this heading#Mulai penterjemah interaktif Python.
\nSpecifies the shell to use. By default, Django will use IPython or bpython if\neither is installed. If both are installed, specify which one you want like so:
\nIPython:
\ndjango-admin shell -i ipython\nbpython:
\ndjango-admin shell -i bpython\nIf you have a "rich" shell installed but want to force use of the "plain"\nPython interpreter, use python as the interface name, like so:
django-admin shell -i python\nDisables reading the startup script for the "plain" Python interpreter. By\ndefault, the script pointed to by the PYTHONSTARTUP environment\nvariable or the ~/.pythonrc.py script is read.
Biarkan anda melewatkan perintah sebagai string untuk menjalankan itu sebagai Django, seperti itu:
\ndjango-admin shell --command="import django; print(django.__version__)"\nAnda dapat juga melewatkan kode pada masukan standar untuk menjalankan itu. Sebagai contoh:
\n$ django-admin shell <<EOF\n> import django\n> print(django.__version__)\n> EOF\nPada Windows, REPL adalah keluaran karena batas penerapan dari select.select() pada serambi itu.
showmigrationsLink to this heading#Tampilkan semua perpindahan di sebuah proyek. Anda dapat memilih dari satu dari dua bentuk:
\nLists all of the apps Django knows about, the migrations available for each\napp, and whether or not each migration is applied (marked by an [X] next to\nthe migration name). For a --verbosity of 2 and above, the applied\ndatetimes are also shown.
Aplikasi-aplikasi tanpa perpindahan juga didaftarkan, tetapi (no migrations) dicetak dibawah mereka.
Ini adalah bentuk keluaran awal.
\nShows the migration plan Django will follow to apply migrations. Like\n--list, applied migrations are marked by an [X]. For a --verbosity\nof 2 and above, all dependencies of a migration will also be shown.
app_labels arguments limit the output, however, dependencies of provided\napps may also be included.
Menentukan basisdata untuk diuji. Awalan default.
sqlflushLink to this heading#Cetak pernyataan SQL yang akan dijalankan untuk perintah flush.
Menentukan basisdata untuk dimana mencetak SQL. Awal ke default.
sqlflushLink to this heading#Prints the SQL for the named migration. This requires an active database\nconnection, which it will use to resolve constraint names; this means you must\ngenerate the SQL against a copy of the database you wish to later apply it on.
\ncatat bahwa sqlmigrate tidak mewarnai keluarannya.
Generates the SQL for unapplying the migration. By default, the SQL created is\nfor running the migration in the forwards direction.
\nMenentukan basisdata dimana untuk membangkitkan SQL. Awalan pada default.
sqlsequenceresetLink to this heading#Mencetak pernyataan SQL untuk menyetel kembali urutan untuk nama aplikasi yang diberikan.
\nSequences are indexes used by some database engines to track the next available\nnumber for automatically incremented fields.
\nUse this command to generate SQL which will fix cases where a sequence is out\nof sync with its automatically incremented field data.
\nMenentukan basisdata untuk dimana mencetak SQL. Awal ke default.
squashmigrationsLink to this heading#Squashes the migrations for app_label up to and including migration_name\ndown into fewer migrations, if possible. The resulting squashed migrations\ncan live alongside the unsquashed ones safely. For more information,\nplease read Squashing migrations.
When start_migration_name is given, Django will only include migrations\nstarting from and including this migration. This helps to mitigate the\nsquashing limitation of RunPython and\ndjango.db.migrations.operations.RunSQL migration operations.
Disables the optimizer when generating a squashed migration. By default, Django\nwill try to optimize the operations in your migrations to reduce the size of\nthe resulting file. Use this option if this process is failing or creating\nincorrect migrations, though please also file a Django bug report about the\nbehavior, as optimization is meant to be safe.
\nMenekan semua permintaan pengguna.
\nSets the name of the squashed migration. When omitted, the name is based on the\nfirst and last migration, with _squashed_ in between.
Generate squashed migration file without Django version and timestamp header.
\nstartappLink to this heading#Membuat sebuah direktori aplikasi Django untuk nama aplikasi yang diberikan dalam direktori saat ini atau tujuan yang diberikan.
\nBy default, the new directory contains a\nmodels.py file and other app template files. If only the app name is given,\nthe app directory will be created in the current working directory.
Jika tujuan pilihan disediakan, Django akan menggunakan direktori yang ada tersebut daripada membuat satu yang baru. Anda dapat menggunakan '.' untuk menyatakan direktori kerja saat ini.
\nSebagai contoh:
\ndjango-admin startapp myapp /Users/jezdez/Code/myapp\nProvides the path to a directory with a custom app template file, or a path to\nan uncompressed archive (.tar) or a compressed archive (.tar.gz,\n.tar.bz2, .tar.xz, .tar.lzma, .tgz, .tbz2, .txz,\n.tlz, .zip) containing the app template files.
Sebagai contoh, ini akan mencari sebuah cetakan aplikasi dalam direktori yang diberikan ketika membuat aplikasi myapp:
django-admin startapp --template=/Users/jezdez/Code/my_app_template myapp\nDjango juga akan menerima URL (http, https, ftp) untuk menekan arsip dengan berkas cetakan aplikasi, mengunduh dan mengeluarkan mereka dengan cepat.
Sebagai contoh, mengambil keuntungan dari firur Github untuk menyingkap gudang sebagai berkas zip, anda dapat menggunakan URL seperti:
\ndjango-admin startapp --template=https://github.com/githubuser/django-app-template/archive/main.zip myapp\nMenentukan ekstensi berkas mana dalam cetakan aplikasi harus dibangun dengan mesin cetakan. Awalan pada py.
Menentukan berkas-berkas mana dalam cetakan aplikasi (sebagai tambahan ke pencocokan tersebut -extension) harus dibangun dengan mesin cetakan. Awalan pada sebuah list kosong.
Specifies which directories in the app template should be excluded, in addition\nto .git and __pycache__. If this option is not provided, directories\nnamed __pycache__ or starting with . will be excluded.
template context digunakan untuk semua pencocokan berkas adalah:
Pilihan apapun dilewatkan ke perintah startapp (diantara pilihan yang didukugn perintah)
app_name -- nama aplikasi diloloskan ke perintah
app_directory -- jalur penuh dari aplikasi dibuat baru saja
camel_case_app_name -- nama aplikasi dalam bentuk casing onta
docs_version -- versi dari dokumentasi: 'dev' atau '1.x'
django_version -- the version of Django, e.g. '2.0.3'
startprojectLink to this heading#Membuat struktur direktori proyek Django untuk nama proyek yang diberikan dalam direktori saat ini atau tujuanyang diberikan.
\nBy default, the new directory contains\nmanage.py and a project package (containing a settings.py and other\nfiles).
If only the project name is given, both the project directory and project\npackage will be named <projectname> and the project directory\nwill be created in the current working directory.
If the optional destination is provided, Django will use that existing\ndirectory as the project directory, and create manage.py and the project\npackage within it. Use '.' to denote the current working directory.
Sebagai contoh:
\ndjango-admin startproject myproject /Users/jezdez/Code/myproject_repo\nMenentukan sebuah direktori, jalur berkas, atau URL dari penyesuaian cetakan proyek. Lihat dokumentasi startapp --template untuk contoh-contoh dan penggunaan.
Menentukan berkas-berkas tambahan mana dalam proyek harus dibangun dengan mesin cetakan. Awalan pada py.
Specifies which files in the project template (in addition to those matching\n--extension) should be rendered with the template engine. Defaults to an\nempty list.
Specifies which directories in the project template should be excluded, in\naddition to .git and __pycache__. If this option is not provided,\ndirectories named __pycache__ or starting with . will be excluded.
template context digunakan adalah:
Pilihan apapun dilewatkan pada perintah startproject (diantara pilihan yang didukung perintah)
project_name -- nama proyek diloloskan ke perintah
project_directory -- jalur penuh dari proyek dibuat baru
secret_key -- kunci acak untuk pengaturan SECRET_KEY
docs_version -- versi dari dokumentasi: 'dev' atau '1.x'
django_version -- the version of Django, e.g. '2.0.3'
Harap juga lihat rendering warning seperti disebutkan untuk startapp.
testLink to this heading#Jalankan percobaan untuk semua aplikasi terpasang. Lihat Percobaan di Django untuk informasi lebih.
\nBerhenti menjalankan percobaan dan melaporkan kegagalan segera setelah percobaan gagal.
\nMengendalikan kelas pejalan percobaan yang digunakan untuk menjalankan percobaan. Nilai ini menimpa nilai disediakan oleh pengaturan TEST_RUNNER.
Suppresses all user prompts. A typical prompt is a warning about deleting an\nexisting test database.
\nThe test command receives options on behalf of the specified\n--testrunner. These are the options of the default test runner:\nDiscoverRunner.
Preserves the test database between test runs. This has the advantage of\nskipping both the create and destroy actions which can greatly decrease the\ntime to run tests, especially those in a large test suite. If the test database\ndoes not exist, it will be created on the first run and then preserved for each\nsubsequent run. Unless the MIGRATE test setting is\nFalse, any unapplied migrations will also be applied to the test database\nbefore running the test suite.
Randomizes the order of tests before running them. This can help detect tests\nthat aren't properly isolated. The test order generated by this option is a\ndeterministic function of the integer seed given. When no seed is passed, a\nseed is chosen randomly and printed to the console. To repeat a particular test\norder, pass a seed. The test orders generated by this option preserve Django's\nguarantees on test order. They also keep tests grouped\nby test case class.
\nThe shuffled orderings also have a special consistency property useful when\nnarrowing down isolation issues. Namely, for a given seed and when running a\nsubset of tests, the new order will be the original shuffling restricted to the\nsmaller set. Similarly, when adding tests while keeping the seed the same, the\norder of the original tests will be the same in the new order.
\nSorts test cases in the opposite execution order. This may help in debugging\nthe side effects of tests that aren't properly isolated. Grouping by test\nclass is preserved when using this option. This can be used\nin conjunction with --shuffle to reverse the order for a particular seed.
Setel pengaturan DEBUG menjadi True sebelum menjalankan percobaan. Ini mungkin membantu mengatasi masalah kegagalan percobaan.
Mengadakan SQL logging untuk percobaan gagal. Jika --verbosity adalah 2, kemudian permintaan dalam melewatkan percobaan juga keluaran.
Runs tests in separate parallel processes. Since modern processors have\nmultiple cores, this allows running tests significantly faster.
\nUsing --parallel without a value, or with the value auto, runs one test\nprocess per core according to multiprocessing.cpu_count(). You can\noverride this by passing the desired number of processes, e.g.\n--parallel 4, or by setting the DJANGO_TEST_PROCESSES environment\nvariable.
Django distributes test cases — unittest.TestCase subclasses — to\nsubprocesses. If there are fewer test cases than configured processes, Django\nwill reduce the number of processes accordingly.
Setiap pengolahan mendapatkan basisdatanya sendiri. Anda harus memastikan bahwa kasus-kasus percobaan berbeda tidak mengakses sumberdaya sama. Sebagai contoh, kasus-kasus percobaan yang menyentuh sistem berkas harus membuat direktori sementara untuk penggunaan mereka sendiri.
\n\nThis option requires the third-party tblib package to display tracebacks\ncorrectly:
$ python -m pip install tblib\nFitur ini tidak tersedia pada Windows. Itu tidak bekerja dengan salah satu backend basisdata Oracle.
\nIf you want to use pdb while debugging tests, you must disable parallel\nexecution (--parallel=1). You'll see something like bdb.BdbQuit if you\ndon't.
Runs only tests marked with the specified tags.\nMay be specified multiple times and combined with test --exclude-tag.
Tests that fail to load are always considered matching.
\n\nExcludes tests marked with the specified tags.\nMay be specified multiple times and combined with test --tag.
Runs test methods and classes matching test name patterns, in the same way as\nunittest's -k option. Can be specified multiple times.
Spawns a pdb debugger at each test error or failure. If you have it\ninstalled, ipdb is used instead.
Discards output (stdout and stderr) for passing tests, in the same way\nas unittest's --buffer option.
Django automatically calls faulthandler.enable() when starting the\ntests, which allows it to print a traceback if the interpreter crashes. Pass\n--no-faulthandler to disable this behavior.
Outputs timings, including database setup and total run time.
\ntestserverLink to this heading#Runs a Django development server (as in runserver) using data from\nthe given fixture(s).
Sebagai contoh, perintah ini:
\ndjango-admin testserver mydata.json\n...akan melakukan langkah-langkah berikut:
\nBuat basisdata percobaan, seperti digambarkan di Basisdata percobaan.
Populate the test database with fixture data from the given fixtures.\n(For more on fixtures, see the documentation for loaddata above.)
Runs the Django development server (as in runserver), pointed at\nthis newly created test database instead of your production database.
Ini sangat berguna di sejumlah jalan:
\nWhen you're writing unit tests of how your views\nact with certain fixture data, you can use testserver to interact with\nthe views in a web browser, manually.
Let's say you're developing your Django application and have a "pristine"\ncopy of a database that you'd like to interact with. You can dump your\ndatabase to a fixture (using the dumpdata command, explained\nabove), then use testserver to run your web application with that data.\nWith this arrangement, you have the flexibility of messing up your data\nin any way, knowing that whatever data changes you're making are only\nbeing made to a test database.
Note that this server does not automatically detect changes to your Python\nsource code (as runserver does). It does, however, detect changes to\ntemplates.
Specifies a different port, or IP address and port, from the default of\n127.0.0.1:8000. This value follows exactly the same format and serves\nexactly the same function as the argument to the runserver command.
Contoh:
\nUntuk menjalankan peladen percobaan pada port 7000 dengan fixture1 dan fixture2:
django-admin testserver --addrport 7000 fixture1 fixture2\ndjango-admin testserver fixture1 fixture2 --addrport 7000\n(The above statements are equivalent. We include both of them to demonstrate\nthat it doesn't matter whether the options come before or after the fixture\narguments.)
\nTo run on 1.2.3.4:7000 with a test fixture:
django-admin testserver --addrport 1.2.3.4:7000 test\nSuppresses all user prompts. A typical prompt is a warning about deleting an\nexisting test database.
\nSome commands are only available when the django.contrib application that\nimplements them has been\nenabled. This section describes them grouped by\ntheir application.
django.contrib.authLink to this heading#changepasswordLink to this heading#Perintah ini hanya tersedia jika authentication system (django.contrib.auth) Django dipasang.
Allows changing a user's password. It prompts you to enter a new password twice\nfor the given user. If the entries are identical, this immediately becomes the\nnew password. If you do not supply a user, the command will attempt to change\nthe password whose username matches the current user.
\nMenentukan basisdata untuk permintaan untuk pengguna. Awal ke default.
Contoh penggunaan:
\ndjango-admin changepassword ringo\ncreatesuperuserLink to this heading#Perintah ini hanya tersedia jika authentication system (django.contrib.auth) Django dipasang.
Creates a superuser account (a user who has all permissions). This is\nuseful if you need to create an initial superuser account or if you need to\nprogrammatically generate superuser accounts for your site(s).
\nWhen run interactively, this command will prompt for a password for\nthe new superuser account. When run non-interactively, you can provide\na password by setting the DJANGO_SUPERUSER_PASSWORD environment\nvariable. Otherwise, no password will be set, and the superuser account will\nnot be able to log in until a password has been manually set for it.
In non-interactive mode, the\nUSERNAME_FIELD and required\nfields (listed in\nREQUIRED_FIELDS) fall back to\nDJANGO_SUPERUSER_<uppercase_field_name> environment variables, unless they\nare overridden by a command line argument. For example, to provide an email\nfield, you can use DJANGO_SUPERUSER_EMAIL environment variable.
Suppresses all user prompts. If a suppressed prompt cannot be resolved\nautomatically, the command will exit with error code 1.
\nThe username and email address for the new account can be supplied by\nusing the --username and --email arguments on the command\nline. If either of those is not supplied, createsuperuser will prompt for\nit when running interactively.
Specifies the database into which the superuser object will be saved.
\nYou can subclass the management command and override get_input_data() if you\nwant to customize data input and validation. Consult the source code for\ndetails on the existing implementation and the method's parameters. For example,\nit could be useful if you have a ForeignKey in\nREQUIRED_FIELDS and want to\nallow creating an instance instead of entering the primary key of an existing\ninstance.
django.contrib.contenttypesLink to this heading#remove_stale_contenttypesLink to this heading#Printah ini hanya tersedia jika contenttypes app (django.contrib.contenttypes) Django terpasang.
Deletes stale content types (from deleted models) in your database. Any objects\nthat depend on the deleted content types will also be deleted. A list of\ndeleted objects will be displayed before you confirm it's okay to proceed with\nthe deletion.
\nMenentukan basisdata untuk digunakan. Awalan pada default.
Deletes stale content types including ones from previously installed apps that\nhave been removed from INSTALLED_APPS. Defaults to False.
django.contrib.gisLink to this heading#ogrinspectLink to this heading#Perintah ini hanya tersedia jika GeoDjango (django.contrib.gis) terpasang.
Silahkan mengacu ke description nya di dokumentasi GeoDjango.
django.contrib.sessionsLink to this heading#clearsessionsLink to this heading#Dapat berjalan sebagai sebuah pekerjaan cron job atau langsung membersihkan sesi kadaluarsa.
\ndjango.contrib.sitemapsLink to this heading#ping_googleLink to this heading#Perintah ini hanya tersedia jika Sitemaps framework (django.contrib.sitemaps) terpasang.
Silahkan mengacu ke description nya di dokumentasi Sitemap.
django.contrib.staticfilesLink to this heading#collectstaticLink to this heading#Perintah ini hanya tersedia jika:doc:static files application </howto/static-files/index> (django.contrib.staticfiles) terpasang.
Silahkan mengacu ke description in the staticfiles nya di dokumentasi.
findstaticLink to this heading#Perintah ini hanya tersedia jika:doc:static files application </howto/static-files/index> (django.contrib.staticfiles) terpasang.
Harap mengacu pada description nya dalam dokumentasi the staticfiles .
Although some commands may allow their own custom options, every command\nallows for the following options by default:
\nAdds the given filesystem path to the Python import search path. If this\nisn't provided, django-admin will use the PYTHONPATH environment\nvariable.
Pilihan ini tidak diperlukan dalam manage.py, karena itu merawat pengaturan jalur Python untuk anda.
Contoh penggunaan:
\ndjango-admin migrate --pythonpath='/home/djangoprojects/myproject'\nSpecifies the settings module to use. The settings module should be in Python\npackage syntax, e.g. mysite.settings. If this isn't provided,\ndjango-admin will use the DJANGO_SETTINGS_MODULE environment\nvariable.
Pilihan ini belum diperlukan di manage.py, karena itu menggunakan settings.py dari proyek saat ini secara awal.
Contoh penggunaan:
\ndjango-admin migrate --settings=mysite.settings\nDisplays a full stack trace when a CommandError\nis raised. By default, django-admin will show an error message when a\nCommandError occurs and a full stack trace for any other exception.
This option is ignored by runserver.
Contoh penggunaan:
\ndjango-admin migrate --traceback\nMenentukan jumlah pemberitahuan dan informasi mencari kesalahan yang perintah harus cetak ke konsol.
\n0 berarti tidak ada keluaran.
1 berarti keluaran biasa(awalan).
2 berarti keluaran bertele-tele.
3 berarti keluaran bertele-tele sangat.
This option is ignored by runserver.
Contoh penggunaan:
\ndjango-admin migrate --verbosity 2\nDisables colorized command output. Some commands format their output to be\ncolorized. For example, errors will be printed to the console in red and SQL\nstatements will be syntax highlighted.
\nContoh penggunaan:
\ndjango-admin runserver --no-color\nForces colorization of the command output if it would otherwise be disabled\nas discussed in Pewarnaan sintaksis. For example, you may want to pipe\ncolored output to another command.
\nSkips running system checks prior to running the command. This option is only\navailable if the\nrequires_system_checks command\nattribute is not an empty list or tuple.
Contoh penggunaan:
\ndjango-admin migrate --skip-checks\nThe django-admin / manage.py commands will use pretty\ncolor-coded output if your terminal supports ANSI-colored output. It\nwon't use the color codes if you're piping the command's output to\nanother program unless the --force-color option is used.
On Windows 10, the Windows Terminal application, VS Code, and PowerShell\n(where virtual terminal processing is enabled) allow colored output, and are\nsupported by default.
\nUnder Windows, the legacy cmd.exe native console doesn't support ANSI\nescape sequences so by default there is no color output. In this case either of\ntwo third-party libraries are needed:
Install colorama, a Python package that translates ANSI color codes into\nWindows API calls. Django commands will detect its presence and will make use\nof its services to color output just like on Unix-based platforms.\ncolorama can be installed via pip:
...\\> py -m pip install colorama\nInstall ANSICON, a third-party tool that allows cmd.exe to process\nANSI color codes. Django commands will detect its presence and will make use\nof its services to color output just like on Unix-based platforms.
Other modern terminal environments on Windows, that support terminal colors,\nbut which are not automatically detected as supported by Django, may "fake" the\ninstallation of ANSICON by setting the appropriate environmental variable,\nANSICON="on".
Penggunaan warna untuk penyorotan sintaksis dapat disesuaikan. Django mengirim dengan tida warna palet:
\ndark, cocok pada terminals yang menunjukkan teks putih pada latar belakang hitam. Ini adalah palet awalan.
light, cocok pada to terminal yang menunjukkan teks hitam pada latar belakang putih.
nocolor, yang meniadakan penyorotan sintaksis.
You select a palette by setting a DJANGO_COLORS environment\nvariable to specify the palette you want to use. For example, to\nspecify the light palette under a Unix or OS/X BASH shell, you\nwould run the following at a command prompt:
export DJANGO_COLORS="light"\nAnda dapat menyesuaikan warna yang digunakan. Django menentukan sejumlah peran dimana warna digunakan.
\nerror - Sebuah kesalahan besar.
notice - Sebuah kesalahan kecil.
success - Sebuah berhasil.
warning - Sebuah peringatan.
sql_field - nama dari bidang model di SQL.
sql_coltype - Jenis dari bidang model di SQL.
sql_keyword - Sebuah kata kunci SQL.
sql_table - Nama dari sebuah model di SQL.
http_info - A 1XX HTTP Informational server response.
http_success - A 2XX HTTP Success server response.
http_not_modified - A 304 HTTP Not Modified server response.
http_redirect - A 3XX HTTP Redirect server response other than 304.
http_not_found - A 404 HTTP Not Found server response.
http_bad_request - A 4XX HTTP Bad Request server response other than 404.
http_server_error - A 5XX HTTP Server Error response.
migrate_heading - A heading in a migrations management command.
migrate_label - Sebuah nama perpindahan.
Each of these roles can be assigned a specific foreground and\nbackground color, from the following list:
\nhitam
merah
hijau
kuning
biru
magenta
cyan
putih
Setiap warna ini dapat dirubah menggunakan pilihan tampilan berikut:
\ntebal
garis bawah
kedip
reverse
conceal
Sebuah spesifikasi warna mengikuti satu dari pola berikut:
\nrole=fg
role=fg/bg
role=fg,option,option
role=fg/bg,option,option
where role is the name of a valid color role, fg is the\nforeground color, bg is the background color and each option\nis one of the color modifying options. Multiple color specifications\nare then separated by a semicolon. For example:
export DJANGO_COLORS="error=yellow/blue,blink;notice=magenta"\nwould specify that errors be displayed using blinking yellow on blue,\nand notices displayed using magenta. All other color roles would be\nleft uncolored.
\nColors can also be specified by extending a base palette. If you put\na palette name in a color specification, all the colors implied by that\npalette will be loaded. So:
\nexport DJANGO_COLORS="light;error=yellow/blue,blink;notice=magenta"\nwould specify the use of all the colors in the light color palette,\nexcept for the colors for errors and notices which would be\noverridden as specified.
\nIf you use the Bash shell, consider installing the Django bash completion\nscript, which lives in extras/django_bash_completion in the Django source\ndistribution. It enables tab-completion of django-admin and\nmanage.py commands, so you can, for instance...
Ketik django-admin.
Tekan [TAB] untuk melihat semua pilihan tersedia.
Ketik sql, kemudian [TAB], untuk melihat semua pilihan tersedia yang namanya dimulai dengan sql.
Lihat How to create custom django-admin commands untuk bagaimana menambahkan tindakan disesuaikan.
\nThe Python files created by startproject, startapp,\noptimizemigration, makemigrations, and\nsquashmigrations are formatted using the black command if it is\npresent on your PATH.
If you have black globally installed, but do not wish it used for the\ncurrent project, you can set the PATH explicitly:
PATH=path/to/venv/bin django-admin makemigrations\nFor commands using stdout you can pipe the output to black if needed:
django-admin inspectdb | black -\nUntuk memanggil perintah pengelolaan dari kode gunakan call_command.
namenama dari perintah untuk memanggil atau memerintah obyek. Melewatkan nama dipilih meskipun obyek diwajibkan untuk percobaan.
\n*argsa list of arguments accepted by the command. Arguments are passed to the\nargument parser, so you can use the same style as you would on the command\nline. For example, call_command('flush', '--verbosity=0').
**optionsnamed options accepted on the command-line. Options are passed to the command\nwithout triggering the argument parser, which means you'll need to pass the\ncorrect type. For example, call_command('flush', verbosity=0) (zero must\nbe an integer rather than a string).
Contoh:
\nfrom django.core import management\nfrom django.core.management.commands import loaddata\n\nmanagement.call_command('flush', verbosity=0, interactive=False)\nmanagement.call_command('loaddata', 'test_data', verbosity=0)\nmanagement.call_command(loaddata.Command(), 'test_data', verbosity=0)\nNote that command options that take no arguments are passed as keywords\nwith True or False, as you can see with the interactive option above.
Named arguments can be passed by using either one of the following syntaxes:
\n# Similar to the command line\nmanagement.call_command('dumpdata', '--natural-foreign')\n\n# Named argument similar to the command line minus the initial dashes and\n# with internal dashes replaced by underscores\nmanagement.call_command('dumpdata', natural_foreign=True)\n\n# `use_natural_foreign_keys` is the option destination variable\nmanagement.call_command('dumpdata', use_natural_foreign_keys=True)\nSome command options have different names when using call_command() instead\nof django-admin or manage.py. For example, django-admin\ncreatesuperuser --no-input translates to call_command('createsuperuser',\ninteractive=False). To find what keyword argument name to use for\ncall_command(), check the command's source code for the dest argument\npassed to parser.add_argument().
Command options which take multiple options are passed a list:
\nmanagement.call_command('dumpdata', exclude=['contenttypes', 'auth'])\nThe return value of the call_command() function is the same as the return\nvalue of the handle() method of the command.
Note that you can redirect standard output and error streams as all commands\nsupport the stdout and stderr options. For example, you could write:
with open('/path/to/command_output', 'w') as f:\n management.call_command('dumpdata', stdout=f)\n