# Dokumentasi Django 5.2.8

# `django-admin` dan `manage.py`

`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 does the same thing as `django-admin` but also sets the `DJANGO_SETTINGS_MODULE` environment variable so that it points to your project's `settings.py` file.

The `django-admin` script should be on your system path if you installed Django via `pip`. If it's not in your path, ensure you have your virtual environment 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.

## Penggunaan

/ 

    $ django-admin <command> [options]
    $ manage.py <command> [options]
    $ python -m django <command> [options]

    ...\> django-admin <command> [options]
    ...\> manage.py <command> [options]
    ...\> py -m django <command> [options]

`command` harys berupa satu dari perintah terdaftar dalam dokumen ini. `options`, yaitu pilihan, harus berupa nol atau lebih dari pilihan tersedia untuk perintah yang diberikan.

### Mendapatkan bantuan dijalankan

django-admin help

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.

### Nama aplikasi

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`.

### Menentukan versi

django-admin version

Jalankan `django-admin version` untuk menjalankan versi Django saat ini.

The output follows the schema described in PEP 440:

    1.4.dev17026
    1.4a1
    1.4

### Menampilkan keluaran mencari kesalahan

Use `--verbosity`, where it is supported, to specify the amount of notification and debug information that `django-admin` prints to the console.

## Perintah tersedia

### `check`

django-admin check [app_label [app_label ...]]

Menggunakan system check framework untuk memeriksa keseluruhan proyek Django untuk masalah-masalah umum.

By default, all apps will be checked. You can check a subset of apps by providing a list of app labels as arguments:

    django-admin check auth admin myapp

--tag TAGS, -t TAGS

The system check framework performs many different types of checks that are categorized with tags. You can use these tags to restrict the checks performed to just those in a particular category. For example, to perform only models and compatibility checks, run:

    django-admin check --tag models --tag compatibility

--database DATABASE

Specifies the database to run checks requiring database access:

    django-admin check --database default --database other

By default, these checks will not be run.

--list-tags

Daftarkan semua etiket tersedia.

--deploy

Mengaktifkan beberapa pemeriksaan tambahan yang hanya bersangkutan dalam pengaturan pengembangan.

You can use this option in your local development environment, but since your local development settings module may not have many of your production settings, you will probably want to point the `check` command at a different settings module, either by setting the `DJANGO_SETTINGS_MODULE` environment variable, or by passing the `--settings` option:

    django-admin check --deploy --settings=production_settings

Atau 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.

--fail-level {CRITICAL,ERROR,WARNING,INFO,DEBUG}

Menentukan tingkat pesan yang akan menyebabkan perintah keluar dengan keadaan bukan-nol. Awalan adalah `ERROR`.

### `compilemessages`

django-admin compilemessages

Menyusun berkas-berkas `.po` dibuat oleh `makemessages` untuk berkas-berkas `.mo` untuk digunakan dengan dukungan gettext siap-pakai. Lihat Internasionalisasi dan lokalisasi.

--locale LOCALE, -l LOCALE

Menentukan lokal-loka untuk diolah. Jika tidak disediakan, semua lokal-lokal adalah terolah.

--exclude EXCLUDE, -x EXCLUDE

Menentukan lokal untuk tidak menyertakan dari pengolahan. jika tidak disediakan, tidak ada lokal tidak disertakan.

--use-fuzzy, -f

Includes fuzzy translations into compiled files.

Contoh penggunaan:

    django-admin compilemessages --locale=pt_BR
    django-admin compilemessages --locale=pt_BR --locale=fr -f
    django-admin compilemessages -l pt_BR
    django-admin compilemessages -l pt_BR -l fr --use-fuzzy
    django-admin compilemessages --exclude=pt_BR
    django-admin compilemessages --exclude=pt_BR --exclude=fr
    django-admin compilemessages -x pt_BR
    django-admin compilemessages -x pt_BR -x fr

--ignore PATTERN, -i PATTERN

Ignores directories matching the given `glob`-style pattern. Use multiple times to ignore more.

Contoh penggunaan:

    django-admin compilemessages --ignore=cache --ignore=outdated/*/locale

### `createcachetable`

django-admin createcachetable

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.

--database DATABASE

Menentukan basisdata dimana tabel-tabel penyimpanan sementara akan dibuat. Awalan pada `default`.

--dry-run

Mencetak SQL yang akan dijalankan tanpa sebenarnya menjalankan itu, sehingga anda dapat menyesuaikan itu atau menggunakan kerangka kerja perpindahan.

### `dbshell`

django-admin dbshell

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 the program name (`psql`, `mysql`, `sqlite3`, `sqlplus`) will find the program in the right place. There's no way to specify the location of the program manually.

--database DATABASE

Menentukan basisdalam kedalam dimana membuka sebuah cangkang. Awalan pada `default`.

-- ARGUMENTS

Any arguments following a `--` divider will be passed on to the underlying command-line client. For example, with PostgreSQL you can use the `psql` command's `-c` flag to execute a raw SQL query directly:

/ 

    $ django-admin dbshell -- -c 'select current_user'
     current_user
    --------------
     postgres
    (1 row)

    ...\> django-admin dbshell -- -c 'select current_user'
     current_user
    --------------
     postgres
    (1 row)

On MySQL/MariaDB, you can do this with the `mysql` command's `-e` flag:

/ 

    $ django-admin dbshell -- -e "select user()"
    +----------------------+
    | user()               |
    +----------------------+
    | djangonaut@localhost |
    +----------------------+

    ...\> django-admin dbshell -- -e "select user()"
    +----------------------+
    | user()               |
    +----------------------+
    | djangonaut@localhost |
    +----------------------+

Catatan

Be aware that not all options set in the `OPTIONS` part of your database configuration in `DATABASES` are passed to the command-line client, e.g. `'isolation_level'`.

### `diffsettings`

django-admin diffsettings

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`.

--all

Menampilkan semua pengaturan, bahkan jika mereka memiliki nilai awalan Django. Pengaturan seperti itu diawali oleh `"###"`.

--default MODULE

Modul pengaturan untuk membandingkan terhadap pengaturan saat ini. Biarkan kosong untuk membandingkan terhadap pengaturan awalan Django.

--output {hash,unified}

Menentukan 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.

### `dumpdata`

django-admin dumpdata [app_label[.ModelName] [app_label[.ModelName] ...]]

Keluaran pada standar pengeluaran semua data dalam basisdata terkait dengan aplikasi bernama.

Jika tidak ada nama aplikasi disediakan, semua aplikasi terpasang akan dibuang.

Keluaran dari `dumpdata` dapat digunakan sebagai masukan untuk `loaddata`.

When result of `dumpdata` is saved as a file, it can serve as a fixture for tests or as an initial data.

Note that `dumpdata` uses the default manager on the model for selecting the records to dump. If you're using a custom manager as the default manager and it filters some of the available records, not all of the objects will be dumped.

--all, -a

Menggunakan pengelola dasar Django, membuang rekaman yang mungkin sebaliknya disaring atau dirubah oleh pengelola penyesuaian.

--format FORMAT

Menentukan bentuk serialisasi dari keluaran. Awalan pada JSON. Bentuk-bentuk didukung didaftarkan dalam Bentuk-bentuk serialisasi.

--indent INDENT

Menentukan angka dari lekukan ruang untuk digunakan dalam keluaran. Awalan pada `None` yang menampilkan semua data dalam baris tunggal.

--exclude EXCLUDE, -e EXCLUDE

Prevents specific applications or models (specified in the form of `app_label.ModelName`) from being dumped. If you specify a model name, then only that model will be excluded, rather than the entire application. You can also mix application names and model names.

If you want to exclude multiple applications, pass `--exclude` more than once:

    django-admin dumpdata --exclude=auth --exclude=contenttypes

--database DATABASE

Menentukan basisdata dari data mana akan dibuang. Awalan pada `default`.

--natural-foreign

Uses the `natural_key()` model method to serialize any foreign key and many-to-many relationship to objects of the type that defines the method. If you're dumping `contrib.auth` `Permission` objects or `contrib.contenttypes` `ContentType` objects, you should probably use this flag. See the natural keys documentation for more details on this and the next option.

--natural-primary

Menghilangkan primary key dalam penserialan data dari obyek ini sejak itu dapat dihitung selama pendeserialisasi.

--pks PRIMARY_KEYS

Outputs only the objects specified by a comma separated list of primary keys. This is only available when dumping one model. By default, all the records of the model are output.

--output OUTPUT, -o OUTPUT

Menentukan sebuah berkas untuk menulis data terserialisasi. Secara awalan, data pergi ke keluaran standar.

Ketika pilihan ini disetel dan `--verbosity` lebih besar dari 0 (awalan), sebuah batang kemajuan ditampilkan dalam terminal.

#### Fixtures compression

The output file can be compressed with one of the `bz2`, `gz`, `lzma`, or `xz` formats by ending the filename with the corresponding extension. For example, to output the data as a compressed JSON file:

    django-admin dumpdata -o mydata.json.gz

### `flush`

django-admin flush

Removes all data from the database and re-executes any post-synchronization handlers. The table of which migrations have been applied is not cleared.

If you would rather start from an empty database and rerun all migrations, you should drop and recreate the database and then run `migrate` instead.

--noinput, --no-input

Menekan semua permintaan pengguna.

--database DATABASE

Menentukan basisdata untuk dialirkan. Awalan pada `default`.

### `inspectdb`

django-admin inspectdb [table [table ...]]

Introspects the database tables in the database pointed-to by the `NAME` setting and outputs a Django model module (a `models.py` file) to standard output.

You may choose what tables or views to inspect by passing their names as arguments. If no arguments are provided, models are created for views only if the `--include-views` option is used. Models for partition tables are created 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.

As you might expect, the created models will have an attribute for every field in the table. Note that `inspectdb` has a few special cases in its field-name output:

- If `inspectdb` cannot map a column's type to a model field type, it'll use `TextField` and will insert the Python comment `'This field type is a guess.'` next to the field in the generated model. The recognized fields may depend on apps listed in `INSTALLED_APPS`. For example, `django.contrib.postgres` adds recognition for several PostgreSQL-specific field types.

- If the database column name is a Python reserved word (such as `'pass'`, `'class'` or `'for'`), `inspectdb` will append `'_field'` to the attribute name. For example, if a table has a column `'for'`, the generated model will have a field `'for_field'`, with the `db_column` attribute set to `'for'`. `inspectdb` will insert the Python comment `'Field renamed because it was a Python reserved word.'` next to the field.

This feature is meant as a shortcut, not as definitive model generation. After you run it, you'll want to look over the generated models yourself to make customizations. In particular, you'll need to rearrange models' order, so that models that refer to other models are ordered properly.

Django doesn't create database defaults when a `default` is specified on a model field. Similarly, database defaults aren't translated to model field defaults or detected in any fashion by `inspectdb`.

By default, `inspectdb` creates unmanaged models. That is, `managed = False` in the model's `Meta` class tells Django not to manage each table's creation, modification, and deletion. If you do want to allow Django to manage the table's lifecycle, you'll need to change the `managed` option to `True` (or remove it because `True` is its default value).

#### Catatan khusus-basisdata

##### Oracle

- Model-model dibuat untuk mewujudkan tampilan jika `--include-views` digunakan.

##### PostgreSQL

- 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.

--database DATABASE

Menentukan basisdata untuk mawas diri. Awalan pada `default`.

--include-partitions

Jika pilihan ini disediakan, model juga dibuat untuk penyekatan.

Hanya mendukung untuk PostgreSQL dijalankan.

--include-views

Jika pilihan ini disediakan, model juga dibuat untuk tampilan basisdata.

### `loaddata`

django-admin loaddata fixture [fixture ...]

Searches for and loads the contents of the named fixture into the database.

--database DATABASE

Menentukan basisdata dimana data akan dimuat. Awalan pada `default`.

--ignorenonexistent, -i

Ignores fields and models that may have been removed since the fixture was originally generated.

--app APP_LABEL

Specifies a single app to look for fixtures in rather than looking in all apps.

--format FORMAT

Menentukan serialization format (misalnya, `json` atau `xml`) untuk fixture read from stdin.

--exclude EXCLUDE, -e EXCLUDE

Excludes loading the fixtures from the given applications and/or models (in the form of `app_label` or `app_label.ModelName`). Use the option multiple times to exclude more than one app or model.

#### memuat fixture dari `stdin`

You can use a dash as the fixture name to load input from `sys.stdin`. For example:

    django-admin loaddata --format=json -

When reading from `stdin`, the `--format` option is required to specify the serialization format of the input (e.g., `json` or `xml`).

Loading from `stdin` is useful with standard input and output redirections. For example:

    django-admin dumpdata --format=json --database=test app_label.ModelName | django-admin loaddata --format=json --database=prod -

Perintah `dumpdata` dapat digunakan untuk membangkitkan masukan untuk `loaddata`.

Lihat juga

For more detail about fixtures see the Perlengkapan topic.

### `makemessages`

django-admin makemessages

Runs over the entire source tree of the current directory and pulls out all strings marked for translation. It creates (or updates) a message file in the conf/locale (in the Django tree) or locale (for project and application) directory. After making changes to the messages files you need to compile them with `compilemessages` for use with the builtin gettext support. See the i18n documentation for details.

This command doesn't require configured settings. However, when settings aren't configured, the command can't ignore the `MEDIA_ROOT` and `STATIC_ROOT` directories or include `LOCALE_PATHS`.

--all, -a

Perbaharui berkas pesan untuk semua bahasa tersedia.

--extension EXTENSIONS, -e EXTENSIONS

Specifies a list of file extensions to examine (default: `html`, `txt`, `py` or `js` if `--domain` is `djangojs`).

Contoh penggunaan:

    django-admin makemessages --locale=de --extension xhtml

Separate multiple extensions with commas or use `-e` or `--extension` multiple times:

    django-admin makemessages --locale=de --extension=html,txt --extension xml

--locale LOCALE, -l LOCALE

Menentukan lokal untuk diolah.

--exclude EXCLUDE, -x EXCLUDE

Menentukan lokal untuk tidak menyertakan dari pengolahan. jika tidak disediakan, tidak ada lokal tidak disertakan.

Contoh penggunaan:

    django-admin makemessages --locale=pt_BR
    django-admin makemessages --locale=pt_BR --locale=fr
    django-admin makemessages -l pt_BR
    django-admin makemessages -l pt_BR -l fr
    django-admin makemessages --exclude=pt_BR
    django-admin makemessages --exclude=pt_BR --exclude=fr
    django-admin makemessages -x pt_BR
    django-admin makemessages -x pt_BR -x fr

--domain DOMAIN, -d DOMAIN

Menentukan ranah dari berkas pesan. Pilihan didukung adalah:

- Berkas-berkas `django` for all `*.py`, `*.html` and ``*.txt``(awal)

- `djangojs` untuk berkas-berkas `*.js`

--symlinks, -s

Follows symlinks to directories when looking for new translation strings.

Contoh penggunaan:

    django-admin makemessages --locale=de --symlinks

--ignore PATTERN, -i PATTERN

Ignores files or directories matching the given `glob`-style pattern. Use multiple times to ignore more.

Pola ini digunakan secara awalan: `'CVS'`, `'.*'`, `'*~'`, `'*.pyc'`.

Contoh penggunaan:

    django-admin makemessages --locale=en_US --ignore=apps/* --ignore=secret/*.html

--no-default-ignore

Meniadakan nilai awalan dari `--ignore`.

--no-wrap

Disables breaking long message lines into several lines in language files.

--no-location

Suppresses writing '`#: filename:line`’ comment lines in language files. Using this option makes it harder for technically skilled translators to understand each message's context.

--add-location [{full,file,never}]

Controls `#: filename:line` comment lines in language files. If the option is:

- `full` (the default if not given): the lines include both file name and line number.

- `file`: nomor baris dihilangkan.

- `never`: baris-baris ditekan (sama seperti `--no-location`).

Dibtuhkan `gettext` 0.19 atau terbaru.

--no-obsolete

Removes obsolete message strings from the `.po` files.

--keep-pot

Prevents deleting the temporary `.pot` files generated before creating the `.po` file. This is useful for debugging errors which may prevent the final language files from being created.

Lihat juga

Lihat Menyesuaikan perintah makemessages untuk petunjuk pada bagaimana menyesuaikan kata kunci yang `makemessages` lewatkan ke `xgettext`.

### `makemigrations`

django-admin makemigrations [app_label [app_label ...]]

Creates new migrations based on the changes detected to your models. Migrations, their relationship with apps and more are covered in depth in the migrations documentation.

Providing one or more app names as arguments will limit the migrations created to the app(s) specified and any dependencies needed (the table at the other end of a `ForeignKey`, for example).

To add migrations to an app that doesn't have a `migrations` directory, run `makemigrations` with the app's `app_label`.

--noinput, --no-input

Suppresses all user prompts. If a suppressed prompt cannot be resolved automatically, the command will exit with error code 3.

--empty

Outputs an empty migration for the specified apps, for manual editing. This is for advanced users and should not be used unless you are familiar with the migration format, migration operations, and the dependencies between your migrations.

--dry-run

Shows what migrations would be made without actually writing any migrations files to disk. Using this option along with `--verbosity 3` will also show the complete migrations files that would be written.

--merge

Mengadakan perbaikan dari pertentangan perpindahan.

--name NAME, -n NAME

Allows naming the generated migration(s) instead of using a generated name. The name must be a valid Python identifier.

--no-header

Membangkitkan berkas-berkas perpindahan tanpa versi Django dan kepala timestamp.

--check

Makes `makemigrations` exit with a non-zero status when model changes without migrations are detected. Implies `--dry-run`.

--scriptable

Diverts log output and input prompts to `stderr`, writing only paths of generated migration files to `stdout`.

--update

Merges model changes into the latest migration and optimize the resulting operations.

The updated migration will have a generated name. In order to preserve the previous name, set it using `--name`.

### `migrate`

django-admin migrate [app_label] [migration_name]

Synchronizes the database state with the current set of models and migrations. Migrations, their relationship with apps and more are covered in depth in the migrations documentation.

Kebiasaan dari perintah ini berubah tergantung pada argumen disediakan:

- Tidak ada argumen: Semua aplikasi mempunyai semua perpindahan mereka berjalan.

- `<app_label>`: The specified app has its migrations run, up to the most recent migration. This may involve running other apps' migrations too, due to dependencies.

- `<app_label> <migrationname>`: Brings the database schema to a state where the named migration is applied, but no later migrations in the same app are applied. This may involve unapplying migrations if you have previously migrated past the named migration. You can use a prefix of the migration name, e.g. `0001`, as long as it's unique for the given app name. Use the name `zero` to migrate all the way back i.e. to revert all applied migrations for an app.

Peringatan

When unapplying migrations, all dependent migrations will also be unapplied, regardless of `<app_label>`. You can use `--plan` to check which migrations will be unapplied.

--database DATABASE

Menentukan basisdata untuk perpindahan. Awal ke `default`.

--fake

Marks the migrations up to the target one (following the rules above) as applied, but without actually running the SQL to change your database schema.

This is intended for advanced users to manipulate the current migration state directly if they're manually applying changes; be warned that using `--fake` runs the risk of putting the migration state table into a state where manual recovery will be needed to make migrations run correctly.

--fake-initial

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.

--plan

Shows the migration operations that will be performed for the given `migrate` command.

--run-syncdb

Allows creating tables for apps without migrations. While this isn't recommended, the migrations framework is sometimes too slow on large projects with hundreds of models.

--noinput, --no-input

Suppresses all user prompts. An example prompt is asking about removing stale content types.

--check

Makes `migrate` exit with a non-zero status when unapplied migrations are detected.

--prune

Deletes nonexistent migrations from the `django_migrations` table. This is useful when migration files replaced by a squashed migration have been removed. See Menginjak perpindahan for more details.

### `optimizemigration`

django-admin optimizemigration app_label migration_name

Optimizes the operations for the named migration and overrides the existing file. If the migration contains functions that must be manually copied, the command creates a new migration file suffixed with `_optimized` that is meant to replace the named migration.

--check

Makes `optimizemigration` exit with a non-zero status when a migration can be optimized.

### `runserver`

django-admin runserver [addrport]

Starts a lightweight development web server on the local machine. By default, the server runs on port 8000 on the IP address `127.0.0.1`. You can pass in an IP address and port number explicitly.

If you run this script as a user with normal privileges (recommended), you might not have access to start a port on a low port number. Low port numbers are reserved for the superuser (root).

Peladen ini menggunakan obyek aplikasi WSGI ditentukan oleh pengaturan `WSGI_APPLICATION`.

Peringatan

DO NOT USE THIS SERVER IN A PRODUCTION SETTING.

This lightweight development server has not gone through security audits or performance tests, hence is unsuitable for production. Making this server able to handle a production environment is outside the scope of Django.

The development server automatically reloads Python code for each request, as needed. You don't need to restart the server for code changes to take effect. However, some actions like adding files don't trigger a restart, so you'll have to restart the server in these cases.

If you're using Linux or MacOS and install both pywatchman and the Watchman service, kernel signals will be used to autoreload the server (rather than polling file modification timestamps each second). This offers better performance on large projects, reduced response time after code changes, more robust change detection, and a reduction in power usage. Django supports `pywatchman` 1.2.0 and higher.

Direktori besar dengan banyak berkas mungkin menyebabkan masalah-masalah penampilan

When using Watchman with a project that includes large non-Python directories like `node_modules`, it's advisable to ignore this directory for optimal performance. See the watchman documentation for information on how to do this.

Watchman timeout

DJANGO_WATCHMAN_TIMEOUT

The default timeout of `Watchman` client is 5 seconds. You can change it by setting the `DJANGO_WATCHMAN_TIMEOUT` environment variable.

When you start the server, and each time you change Python code while the server is running, the system check framework will check your entire Django project for some common errors (see the `check` command). If any errors are found, they will be printed to standard output. You can use the `--skip-checks` option to skip running system checks.

You can run as many concurrent servers as you want, as long as they're on separate ports by executing `django-admin runserver` more than once.

Note that the default IP address, `127.0.0.1`, is not accessible from other machines on your network. To make your development server viewable to other machines on the network, use its own IP address (e.g. `192.168.2.1`), `0` (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.

Jika 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 django.server logger.

--noreload

Disables the auto-reloader. This means any Python code changes you make while the server is running will not take effect if the particular Python modules have already been loaded into memory.

--nothreading

Disables use of threading in the development server. The server is multithreaded by default.

--ipv6, -6

Menggunakan IPv6 untuk peladen pengembangan. Ini merubah alamat IP awal dari `127.0.0.1` ke `::1`.

DJANGO_RUNSERVER_HIDE_WARNING

New in Django 5.2.

By default, a warning is printed to the console that `runserver` is not suitable for production:

    WARNING: This is a development server. Do not use it in a production setting. Use a production WSGI or ASGI server instead.
    For more information on production servers see: https://docs.djangoproject.com/en/|version|/howto/deployment/

Set this environment variable to `"true"` to hide this warning.

#### Contoh dari menggunakan port dan alamat berbeda

Port 8000 on IP address `127.0.0.1`:

    django-admin runserver

Port 8000 on IP address `1.2.3.4`:

    django-admin runserver 1.2.3.4:8000

Port 7000 on IP address `127.0.0.1`:

    django-admin runserver 7000

Port 7000 on IP address `1.2.3.4`:

    django-admin runserver 1.2.3.4:7000

Port 8000 on IPv6 address `::1`:

    django-admin runserver -6

Port 7000 on IPv6 address `::1`:

    django-admin runserver -6 7000

Port 7000 on IPv6 address `2001:0db8:1234:5678::9`:

    django-admin runserver [2001:0db8:1234:5678::9]:7000

Port 8000 on IPv4 address of host `localhost`:

    django-admin runserver localhost:8000

Port 8000 on IPv6 address of host `localhost`:

    django-admin runserver -6 localhost:8000

#### Melayani berkas-berkas statis dengan peladen pengembangan

By default, the development server doesn't serve any static files for your site (such as CSS files, images, things under `MEDIA_URL` and so forth). If you want to configure Django to serve static media, read Bagaimana mengelola berkas statik (misalnya gambar, JavaScript, CSS).

#### Serving with ASGI in development

Django's `runserver` command provides a WSGI server. In order to run under ASGI you will need to use an ASGI server. The Django Daphne project provides Integrasi dengan runserver that you can use.

### `sendtestemail`

django-admin sendtestemail [email [email ...]]

Sends a test email (to confirm email sending through Django is working) to the recipient(s) specified. For example:

    django-admin sendtestemail foo@example.com bar@example.com

Ada sepasang pilihan, dan anda mungkin menggunakan perpaduan apapun dari mereka bersama-sama:

--managers

Mails the email addresses specified in `MANAGERS` using `mail_managers()`.

--admins

Mails the email addresses specified in `ADMINS` using `mail_admins()`.

### `sendtestemail`

django-admin shell

Mulai penterjemah interaktif Python.

All models from installed apps are automatically imported into the shell environment. Models from apps listed earlier in `INSTALLED_APPS` take precedence. The following common utilities are also imported:

    from django.db import connection, reset_queries, models
    from django.conf import settings
    from django.utils import timezone

For a `--verbosity` of 2 or higher, the automatically imported objects will be listed. To disable automatic importing entirely, use the `--no-imports` flag.

See the guide on customizing this behavior to add or remove automatic imports.

Changed in Django 5.2:

Automatic models import was added.

Changed in Django 6.0:

Automatic imports of common utilities, such as `django.conf.settings`, were added.

--interface {ipython,bpython,python}, -i {ipython,bpython,python}

Specifies the shell to use. By default, Django will use IPython or bpython if either is installed. If both are installed, specify which one you want like so:

IPython:

    django-admin shell -i ipython

bpython:

    django-admin shell -i bpython

If you have a "rich" shell installed but want to force use of the "plain" Python interpreter, use `python` as the interface name, like so:

    django-admin shell -i python

--no-startup

Disables reading the startup script for the "plain" Python interpreter. By default, the script pointed to by the `PYTHONSTARTUP` environment variable or the `~/.pythonrc.py` script is read.

--no-imports

New in Django 5.2.

Disables the automatic import of models from `INSTALLED_APPS`.

--command COMMAND, -c COMMAND

Lets you pass a command as a string to execute it as Django, like so:

    django-admin shell --command="import django; print(django.__version__)"

Anda dapat juga melewatkan kode pada masukan standar untuk menjalankan itu. Sebagai contoh:

    $ django-admin shell <<EOF
    > import django
    > print(django.__version__)
    > EOF

Pada Windows, REPL adalah keluaran karena batas penerapan dari `select.select()` pada serambi itu.

### `showmigrations`

django-admin showmigrations [app_label [app_label ...]]

Tampilkan semua perpindahan di sebuah proyek. Anda dapat memilih dari satu dari dua bentuk:

--list, -l

Lists all of the apps Django knows about, the migrations available for each app, and whether or not each migration is applied (marked by an `[X]` next to the migration name). For a `--verbosity` of 2 and above, the applied datetimes are also shown.

Aplikasi-aplikasi tanpa perpindahan juga didaftarkan, tetapi `(no migrations)` dicetak dibawah mereka.

Ini adalah bentuk keluaran awal.

--plan, -p

Shows the migration plan Django will follow to apply migrations. Like `--list`, applied migrations are marked by an `[X]`. For a `--verbosity` of 2 and above, all dependencies of a migration will also be shown.

`app_label`s arguments limit the output, however, dependencies of provided apps may also be included.

--database DATABASE

Menentukan basisdata untuk diuji. Awalan `default`.

### `sqlflush`

django-admin sqlflush

Cetak pernyataan SQL yang akan dijalankan untuk perintah `flush`.

--database DATABASE

Menentukan basisdata untuk dimana mencetak SQL. Awal ke `default`.

### `sqlflush`

django-admin sqlmigrate app_label migration_name

Prints the SQL for the named migration. This requires an active database connection, which it will use to resolve constraint names; this means you must generate the SQL against a copy of the database you wish to later apply it on.

catat bahwa `sqlmigrate` tidak mewarnai keluarannya.

--backwards

Generates the SQL for unapplying the migration. By default, the SQL created is for running the migration in the forwards direction.

--database DATABASE

Menentukan basisdata dimana untuk membangkitkan SQL. Awalan pada `default`.

### `sqlsequencereset`

django-admin sqlsequencereset app_label [app_label ...]

Mencetak pernyataan SQL untuk menyetel kembali urutan untuk nama aplikasi yang diberikan.

Sequences are indexes used by some database engines to track the next available number for automatically incremented fields.

Use this command to generate SQL which will fix cases where a sequence is out of sync with its automatically incremented field data.

--database DATABASE

Menentukan basisdata untuk dimana mencetak SQL. Awal ke `default`.

### `squashmigrations`

django-admin squashmigrations app_label [start_migration_name] migration_name

Squashes the migrations for `app_label` up to and including `migration_name` down into fewer migrations, if possible. The resulting squashed migrations can live alongside the unsquashed ones safely. For more information, please read Menginjak perpindahan.

When `start_migration_name` is given, Django will only include migrations starting from and including this migration. This helps to mitigate the squashing limitation of `RunPython` and `django.db.migrations.operations.RunSQL` migration operations.

--no-optimize

Disables the optimizer when generating a squashed migration. By default, Django will try to optimize the operations in your migrations to reduce the size of the resulting file. Use this option if this process is failing or creating incorrect migrations, though please also file a Django bug report about the behavior, as optimization is meant to be safe.

--noinput, --no-input

Menekan semua permintaan pengguna.

--squashed-name SQUASHED_NAME

Sets the name of the squashed migration. When omitted, the name is based on the first and last migration, with `_squashed_` in between.

--no-header

Generate squashed migration file without Django version and timestamp header.

### `startapp`

django-admin startapp name [directory]

Membuat sebuah direktori aplikasi Django untuk nama aplikasi yang diberikan dalam direktori saat ini atau tujuan yang diberikan.

By default, the new directory contains a `models.py` file and other app template files. If only the app name is given, the app directory will be created in the current working directory.

If the optional destination is provided, Django will use that name instead. If the directory with the given name doesn't exist, it will be created. You can use '.' to denote the current working directory.

Changed in Django 6.0:

Automatic creation of the destination directory was added.

Sebagai contoh:

    django-admin startapp myapp /Users/jezdez/Code/myapp

--template TEMPLATE

Provides the path to a directory with a custom app template file, or a path to an uncompressed archive (`.tar`) or a compressed archive (`.tar.gz`, `.tar.bz2`, `.tar.xz`, `.tar.lzma`, `.tgz`, `.tbz2`, `.txz`, `.tlz`, `.zip`) containing the app template files.

For example, this would look for an app template in the given directory when creating the `myapp` app:

    django-admin startapp --template=/Users/jezdez/Code/my_app_template myapp

Django juga akan menerima URL (`http`, `https`, `ftp`) untuk menekan arsip dengan berkas cetakan aplikasi, mengunduh dan mengeluarkan mereka dengan cepat.

For example, taking advantage of GitHub's feature to expose repositories as zip files, you can use a URL like:

    django-admin startapp --template=https://github.com/githubuser/django-app-template/archive/main.zip myapp

Peringatan

Templates provided via `--template` are used as is. Malicious or poorly constructed templates may introduce security weaknesses or unintended behavior. Compressed archives may also consume excessive resources during extraction, potentially causing crashes or hangs.

Contents of templates should be carefully inspected before use.

--extension EXTENSIONS, -e EXTENSIONS

Menentukan ekstensi berkas mana dalam cetakan aplikasi harus dibangun dengan mesin cetakan. Awalan pada `py`.

--name FILES, -n FILES

Menentukan berkas-berkas mana dalam cetakan aplikasi (sebagai tambahan ke pencocokan tersebut `-extension`) harus dibangun dengan mesin cetakan. Awalan pada sebuah list kosong.

--exclude DIRECTORIES, -x DIRECTORIES

Specifies which directories in the app template should be excluded, in addition to `.git` and `__pycache__`. If this option is not provided, directories named `__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'`

Peringatan

When the app template files are rendered with the Django template engine (by default all `*.py` files), Django will also replace all stray template variables contained. For example, if one of the Python files contains a docstring explaining a particular feature related to template rendering, it might result in an incorrect example.

To work around this problem, you can use the `templatetag` template tag to "escape" the various parts of the template syntax.

In addition, to allow Python template files that contain Django template language syntax while also preventing packaging systems from trying to byte-compile invalid `*.py` files, template files ending with `.py-tpl` will be renamed to `.py`.

Peringatan

The contents of custom app (or project) templates should always be audited before use: Such templates define code that will become part of your project, and this means that such code will be trusted as much as any app you install, or code you write yourself. Further, even rendering the templates is, effectively, executing code that was provided as input to the management command. The Django template language may provide wide access into the system, so make sure any custom template you use is worthy of your trust.

### `startproject`

django-admin startproject name [directory]

Membuat struktur direktori proyek Django untuk nama proyek yang diberikan dalam direktori saat ini atau tujuanyang diberikan.

Secara awalan, the new directory mengandung `manage.py` dan sebuah paket proyek (terdiri `settings.py` dan berkas lain).

If only the project name is given, both the project directory and project package will be named `<projectname>` and the project directory will be created in the current working directory.

If the optional destination is provided, Django will use that name as the project directory, and create `manage.py` and the project package within it. If the directory with the given name doesn't exist, it will be created. Use '.' to denote the current working directory.

Changed in Django 6.0:

Automatic creation of the destination directory was added.

Sebagai contoh:

    django-admin startproject myproject /Users/jezdez/Code/myproject_repo

--template TEMPLATE

Specifies a directory, file path, or URL of a custom project template. See the `startapp --template` documentation for examples and usage. The same security considerations described for `startapp` templates apply here: malicious or poorly constructed templates may introduce weaknesses or consume excessive resources, and templates should be carefully inspected before use.

--extension EXTENSIONS, -e EXTENSIONS

Menentukan berkas-berkas tambahan mana dalam proyek harus dibangun dengan mesin cetakan. Awalan pada `py`.

--name FILES, -n FILES

Specifies which files in the project template (in addition to those matching `--extension`) should be rendered with the template engine. Defaults to an empty list.

--exclude DIRECTORIES, -x DIRECTORIES

Specifies which directories in the project template should be excluded, in addition to `.git` and `__pycache__`. If this option is not provided, directories 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'`

Please also see the rendering warning and trusted code warning as mentioned for `startapp`.

### `test`

django-admin test [test_label [test_label ...]]

Jalankan percobaan untuk semua aplikasi terpasang. Lihat Percobaan di Django untuk informasi lebih.

--failfast

Berhenti menjalankan percobaan dan melaporkan kegagalan segera setelah percobaan gagal.

--testrunner TESTRUNNER

Mengendalikan kelas pejalan percobaan yang digunakan untuk menjalankan percobaan. Nilai ini menimpa nilai disediakan oleh pengaturan `TEST_RUNNER`.

--noinput, --no-input

Suppresses all user prompts. A typical prompt is a warning about deleting an existing test database.

#### Pilihan pejalan percobaan

The `test` command receives options on behalf of the specified `--testrunner`. These are the options of the default test runner: `DiscoverRunner`.

--keepdb

Preserves the test database between test runs. This has the advantage of skipping both the create and destroy actions which can greatly decrease the time to run tests, especially those in a large test suite. If the test database does not exist, it will be created on the first run and then preserved for each subsequent run. Unless the `MIGRATE` test setting is `False`, any unapplied migrations will also be applied to the test database before running the test suite.

--shuffle [SEED]

Randomizes the order of tests before running them. This can help detect tests that aren't properly isolated. The test order generated by this option is a deterministic function of the integer seed given. When no seed is passed, a seed is chosen randomly and printed to the console. To repeat a particular test order, pass a seed. The test orders generated by this option preserve Django's guarantees on test order. They also keep tests grouped by test case class.

The shuffled orderings also have a special consistency property useful when narrowing down isolation issues. Namely, for a given seed and when running a subset of tests, the new order will be the original shuffling restricted to the smaller set. Similarly, when adding tests while keeping the seed the same, the order of the original tests will be the same in the new order.

--reverse, -r

Sorts test cases in the opposite execution order. This may help in debugging the side effects of tests that aren't properly isolated. Grouping by test class is preserved when using this option. This can be used in conjunction with `--shuffle` to reverse the order for a particular seed.

--debug-mode

Setel pengaturan `DEBUG` menjadi `True` sebelum menjalankan percobaan. Ini mungkin membantu mengatasi masalah kegagalan percobaan.

--debug-sql, -d

Mengadakan SQL logging untuk percobaan gagal. Jika `--verbosity` adalah `2`, kemudian permintaan dalam melewatkan percobaan juga keluaran.

--parallel [N]

DJANGO_TEST_PROCESSES

Runs tests in separate parallel processes. Since modern processors have multiple cores, this allows running tests significantly faster.

Using `--parallel` without a value, or with the value `auto`, runs one test process per core according to `multiprocessing.cpu_count()`. You can override this by passing the desired number of processes, e.g. `--parallel 4`, or by setting the `DJANGO_TEST_PROCESSES` environment variable.

Django distributes test cases — `unittest.TestCase` subclasses — to subprocesses. If there are fewer test case classes than configured processes, Django will reduce the number of processes accordingly.

Each process gets its own database. You must ensure that different test case classes don't access the same resources. For instance, test case classes that touch the filesystem should create a temporary directory for their own use.

Catatan

If you have test classes that cannot be run in parallel, you can use `SerializeMixin` to run them sequentially. See Enforce running test classes sequentially.

This option requires the third-party `tblib` package to display tracebacks correctly:

    $ python -m pip install tblib

Fitur ini tidak tersedia pada Windows. Itu tidak bekerja dengan salah satu backend basisdata Oracle.

If you want to use `pdb` while debugging tests, you must disable parallel execution (`--parallel=1`). You'll see something like `bdb.BdbQuit` if you don't.

Peringatan

When test parallelization is enabled and a test fails, Django may be unable to display the exception traceback. This can make debugging difficult. If you encounter this problem, run the affected test without parallelization to see the traceback of the failure.

Ini adalah batasan yang diketahui. Itu muncul dari kebutuhan menserialkan obyek untuk menukarkan mereka diantara pengolahan. Lihat What can be pickled and unpickled? untuk rincian.

--tag TAGS

Runs only tests marked with the specified tags. May be specified multiple times and combined with `test --exclude-tag`.

Tests that fail to load are always considered matching.

--exclude-tag EXCLUDE_TAGS

Excludes tests marked with the specified tags. May be specified multiple times and combined with `test --tag`.

-k TEST_NAME_PATTERNS

Runs test methods and classes matching test name patterns, in the same way as `unittest's -k option`. Can be specified multiple times.

--pdb

Spawns a `pdb` debugger at each test error or failure. If you have it installed, `ipdb` is used instead.

--buffer, -b

Discards output (`stdout` and `stderr`) for passing tests, in the same way as `unittest's --buffer option`.

--no-faulthandler

Django automatically calls `faulthandler.enable()` when starting the tests, which allows it to print a traceback if the interpreter crashes. Pass `--no-faulthandler` to disable this behavior.

--timing

Outputs timings, including database setup and total run time.

--durations N

Shows the N slowest test cases (N=0 for all).

### `testserver`

django-admin testserver [fixture [fixture ...]]

Runs a Django development server (as in `runserver`) using data from the given fixture(s).

For example, this command:

    django-admin testserver mydata.json

...akan melakukan langkah-langkah berikut:

1. Buat basisdata percobaan, seperti digambarkan di Basisdata percobaan.

2. Populate the test database with fixture data from the given fixtures. (For more on fixtures, see the documentation for `loaddata` above.)

3. Runs the Django development server (as in `runserver`), pointed at this newly created test database instead of your production database.

Ini sangat berguna di sejumlah jalan:

- When you're writing unit tests of how your views act with certain fixture data, you can use `testserver` to interact with the views in a web browser, manually.

- Let's say you're developing your Django application and have a "pristine" copy of a database that you'd like to interact with. You can dump your database to a fixture (using the `dumpdata` command, explained above), then use `testserver` to run your web application with that data. With this arrangement, you have the flexibility of messing up your data in any way, knowing that whatever data changes you're making are only being made to a test database.

Note that this server does not automatically detect changes to your Python source code (as `runserver` does). It does, however, detect changes to templates.

--addrport ADDRPORT

Specifies a different port, or IP address and port, from the default of `127.0.0.1:8000`. This value follows exactly the same format and serves exactly the same function as the argument to the `runserver` command.

Contoh:

To run the test server on port 7000 with `fixture1` and `fixture2`:

    django-admin testserver --addrport 7000 fixture1 fixture2
    django-admin testserver fixture1 fixture2 --addrport 7000

(The above statements are equivalent. We include both of them to demonstrate that it doesn't matter whether the options come before or after the fixture arguments.)

To run on 1.2.3.4:7000 with a `test` fixture:

    django-admin testserver --addrport 1.2.3.4:7000 test

--noinput, --no-input

Suppresses all user prompts. A typical prompt is a warning about deleting an existing test database.

## Perintah disediakan oleh aplikasi

Some commands are only available when the `django.contrib` application that implements them has been `enabled`. This section describes them grouped by their application.

### `django.contrib.auth`

#### `changepassword`

django-admin changepassword [<username>]

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 for the given user. If the entries are identical, this immediately becomes the new password. If you do not supply a user, the command will attempt to change the password whose username matches the current user.

--database DATABASE

Menentukan basisdata untuk permintaan untuk pengguna. Awal ke `default`.

Contoh penggunaan:

    django-admin changepassword ringo

#### `createsuperuser`

django-admin createsuperuser

DJANGO_SUPERUSER_PASSWORD

Perintah ini hanya tersedia jika authentication system (`django.contrib.auth`) Django dipasang.

Creates a superuser account (a user who has all permissions). This is useful if you need to create an initial superuser account or if you need to programmatically generate superuser accounts for your site(s).

When run interactively, this command will prompt for a password for the new superuser account. When run non-interactively, you can provide a password by setting the `DJANGO_SUPERUSER_PASSWORD` environment variable. Otherwise, no password will be set, and the superuser account will not be able to log in until a password has been manually set for it.

In non-interactive mode, the `USERNAME_FIELD` and required fields (listed in `REQUIRED_FIELDS`) fall back to `DJANGO_SUPERUSER_<uppercase_field_name>` environment variables, unless they are overridden by a command line argument. For example, to provide an `email` field, you can use `DJANGO_SUPERUSER_EMAIL` environment variable.

--noinput, --no-input

Suppresses all user prompts. If a suppressed prompt cannot be resolved automatically, the command will exit with error code 1.

--username USERNAME

--email EMAIL

The username and email address for the new account can be supplied by using the `--username` and `--email` arguments on the command line. If either of those is not supplied, `createsuperuser` will prompt for it when running interactively.

--database DATABASE

Specifies the database into which the superuser object will be saved.

You can subclass the management command and override `get_input_data()` if you want to customize data input and validation. Consult the source code for details on the existing implementation and the method's parameters. For example, it could be useful if you have a `ForeignKey` in `REQUIRED_FIELDS` and want to allow creating an instance instead of entering the primary key of an existing instance.

### `django.contrib.contenttypes`

#### `remove_stale_contenttypes`

django-admin remove_stale_contenttypes

Printah ini hanya tersedia jika contenttypes app (`django.contrib.contenttypes`) Django terpasang.

Deletes stale content types (from deleted models) in your database. Any objects that depend on the deleted content types will also be deleted. A list of deleted objects will be displayed before you confirm it's okay to proceed with the deletion.

--database DATABASE

Menentukan basisdata untuk digunakan. Awalan pada `default`.

--include-stale-apps

Deletes stale content types including ones from previously installed apps that have been removed from `INSTALLED_APPS`. Defaults to `False`.

### `django.contrib.gis`

#### `ogrinspect`

Perintah ini hanya tersedia jika GeoDjango (`django.contrib.gis`) terpasang.

Silahkan mengacu ke `description` nya di dokumentasi GeoDjango.

### `django.contrib.sessions`

#### `clearsessions`

django-admin clearsessions

Dapat berjalan sebagai sebuah pekerjaan cron job atau langsung membersihkan sesi kadaluarsa.

### `django.contrib.staticfiles`

#### `collectstatic`

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.

#### `findstatic`

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 .

## Pilihan awal

Although some commands may allow their own custom options, every command allows for the following options by default:

--pythonpath PYTHONPATH

Adds the given filesystem path to the Python `sys.path` module attribute. If this isn't provided, `django-admin` will use the `PYTHONPATH` environment variable.

Pilihan ini tidak diperlukan dalam `manage.py`, karena itu merawat pengaturan jalur Python untuk anda.

Contoh penggunaan:

    django-admin migrate --pythonpath='/home/djangoprojects/myproject'

--settings SETTINGS

Specifies the settings module to use. The settings module should be in Python package syntax, e.g. `mysite.settings`. If this isn't provided, `django-admin` will use the `DJANGO_SETTINGS_MODULE` environment variable.

Pilihan ini belum diperlukan di `manage.py`, karena itu menggunakan `settings.py` dari proyek saat ini secara awal.

Contoh penggunaan:

    django-admin migrate --settings=mysite.settings

--traceback

Displays a full stack trace when a `CommandError` is raised. By default, `django-admin` will show an error message when a `CommandError` occurs and a full stack trace for any other exception.

This option is ignored by `runserver`.

Contoh penggunaan:

    django-admin migrate --traceback

--verbosity {0,1,2,3}, -v {0,1,2,3}

Menentukan jumlah pemberitahuan dan informasi mencari kesalahan yang perintah harus cetak ke konsol.

- `0` 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:

    django-admin migrate --verbosity 2

--no-color

Disables colorized command output. Some commands format their output to be colorized. For example, errors will be printed to the console in red and SQL statements will be syntax highlighted.

Contoh penggunaan:

    django-admin runserver --no-color

--force-color

Forces colorization of the command output if it would otherwise be disabled as discussed in Pewarnaan sintaksis. For example, you may want to pipe colored output to another command.

--skip-checks

Skips running system checks prior to running the command. This option is only available if the `requires_system_checks` command attribute is not an empty list or tuple.

Contoh penggunaan:

    django-admin migrate --skip-checks

## Kecermatan tambahan

### Pewarnaan sintaksis

DJANGO_COLORS

The `django-admin` / `manage.py` commands will use pretty color-coded output if your terminal supports ANSI-colored output. It won't use the color codes if you're piping the command's output to another program unless the `--force-color` option is used.

#### Windows support

On Windows 10, the Windows Terminal application, VS Code, and PowerShell (where virtual terminal processing is enabled) allow colored output, and are supported by default.

Under Windows, the legacy `cmd.exe` native console doesn't support ANSI escape sequences so by default there is no color output. In this case either of two third-party libraries are needed:

- Install colorama, a Python package that translates ANSI color codes into Windows API calls. Django commands will detect its presence and will make use of its services to color output just like on Unix-based platforms. `colorama` can be installed via pip:

      ...\> py -m pip install "colorama >= 0.4.6"

- Install ANSICON, a third-party tool that allows `cmd.exe` to process ANSI color codes. Django commands will detect its presence and will make use of its services to color output just like on Unix-based platforms.

Other modern terminal environments on Windows, that support terminal colors, but which are not automatically detected as supported by Django, may "fake" the installation of `ANSICON` by setting the appropriate environmental variable, `ANSICON="on"`.

#### Custom colors

Penggunaan warna untuk penyorotan sintaksis dapat disesuaikan. Django mengirim dengan tida warna palet:

- `dark`, 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 variable to specify the palette you want to use. For example, to specify the `light` palette under a Unix or OS/X BASH shell, you would run the following at a command prompt:

    export DJANGO_COLORS="light"

Anda dapat menyesuaikan warna yang digunakan. Django menentukan sejumlah peran dimana warna digunakan.

- `error` - 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 background color, from the following list:

- `hitam`

- `merah`

- `hijau`

- `kuning`

- `biru`

- `magenta`

- `cyan`

- `putih`

Setiap warna ini dapat dirubah menggunakan pilihan tampilan berikut:

- `tebal`

- `garis bawah`

- `kedip`

- `reverse`

- `conceal`

Sebuah spesifikasi warna mengikuti satu dari pola berikut:

- `role=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 foreground color, `bg` is the background color and each `option` is one of the color modifying options. Multiple color specifications are then separated by a semicolon. For example:

    export DJANGO_COLORS="error=yellow/blue,blink;notice=magenta"

would specify that errors be displayed using blinking yellow on blue, and notices displayed using magenta. All other color roles would be left uncolored.

Colors can also be specified by extending a base palette. If you put a palette name in a color specification, all the colors implied by that palette will be loaded. So:

    export DJANGO_COLORS="light;error=yellow/blue,blink;notice=magenta"

would specify the use of all the colors in the light color palette, except for the colors for errors and notices which would be overridden as specified.

### Bash completion

If you use the Bash shell, consider installing the Django bash completion script, which lives in extras/django_bash_completion in the Django source distribution. It enables tab-completion of `django-admin` and `manage.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 Bagaimana membuat perintah django-admin yang disesuaikan untuk bagaimana menambahkan tindakan disesuaikan.

### Black formatting

The Python files created by `startproject`, `startapp`, `optimizemigration`, `makemigrations`, and `squashmigrations` are formatted using the `black` command if it is present on your `PATH`.

If you have `black` globally installed, but do not wish it used for the current project, you can set the `PATH` explicitly:

    PATH=path/to/venv/bin django-admin makemigrations

For commands using `stdout` you can pipe the output to `black` if needed:

    django-admin inspectdb | black -

# Menjalankan pengelolaan perintah dari kode anda

django.core.management.call_command(name, *args, **options)

To call a management command from code use `call_command()`.

`name`

  nama dari perintah untuk memanggil atau memerintah obyek. Melewatkan nama dipilih meskipun obyek diwajibkan untuk percobaan.

`*args`

  a list of arguments accepted by the command. Arguments are passed to the argument parser, so you can use the same style as you would on the command line. For example, `call_command('flush', '--verbosity=0')`.

`**options`

  named options accepted on the command-line. Options are passed to the command without triggering the argument parser, which means you'll need to pass the correct type. For example, `call_command('flush', verbosity=0)` (zero must be an integer rather than a string).

Contoh:

    from django.core import management
    from django.core.management.commands import loaddata

    management.call_command("flush", verbosity=0, interactive=False)
    management.call_command("loaddata", "test_data", verbosity=0)
    management.call_command(loaddata.Command(), "test_data", verbosity=0)

Note that command options that take no arguments are passed as keywords with `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:

    # Similar to the command line
    management.call_command("dumpdata", "--natural-foreign")

    # Named argument similar to the command line minus the initial dashes and
    # with internal dashes replaced by underscores
    management.call_command("dumpdata", natural_foreign=True)

    # `use_natural_foreign_keys` is the option destination variable
    management.call_command("dumpdata", use_natural_foreign_keys=True)

Some command options have different names when using `call_command()` instead of `django-admin` or `manage.py`. For example, `django-admin createsuperuser --no-input` translates to `call_command('createsuperuser', interactive=False)`. To find what keyword argument name to use for `call_command()`, check the command's source code for the `dest` argument passed to `parser.add_argument()`.

Command options which take multiple options are passed a list:

    management.call_command("dumpdata", exclude=["contenttypes", "auth"])

The return value of the `call_command()` function is the same as the return value of the `handle()` method of the command.

## Pengalihan keluaran

Note that you can redirect standard output and error streams as all commands support the `stdout` and `stderr` options. For example, you could write:

    with open("/path/to/command_output", "w") as f:
        management.call_command("dumpdata", stdout=f)