---
title: "Django 설치하는 법"
version: 5.1
locale: ko
source: https://docs.djangoproject.com/ko/5.1/topics/install/
canonical: https://djangodocs.dev/ko/5.1/topics/install/
---
# Django 설치하는 법

이 문서는 Django를 설치하는 방법을 설명합니다.

## Python 설치

Django is a Python web framework. See [장고와 어떤 파이썬 버전을 사용해야 하나요?](/ko/5.1/faq/install/#faq-python-version-support) for
details.

최신 Python 버전은 <https://www.python.org/downloads/> 또는 운영 체제 패키지 관리자에게 문의하십시오.

> **Windows 환경의 Python**
>
> 만약 Windows를 사용하여 Django를 시작하고 싶다면, :doc:/howto/windows\`를 참고하세요.

## Apache와 `mod_wsgi` 설치

단지 Django를 테스트하고 싶은것 이라면 다음 섹션으로 건너 뛰어도 괜찮습니다. Django는 테스트를 위한 경량의 웹서버를 포함하고 있기때문에 프로덕션 환경에 Django를 배포할 준비가 될때까지 아파치를 설정할 필요는 없습니다.

If you want to use Django on a production site, use [Apache](https://httpd.apache.org/) with
[mod\_wsgi](https://modwsgi.readthedocs.io/en/develop/). mod\_wsgi operates in one of two modes: embedded
mode or daemon mode. In embedded mode, mod\_wsgi is similar to
mod\_perl – it embeds Python within Apache and loads Python code into
memory when the server starts. Code stays in memory throughout the
life of an Apache process, which leads to significant performance
gains over other server arrangements. In daemon mode, mod\_wsgi spawns
an independent daemon process that handles requests. The daemon
process can run as a different user than the web server, possibly
leading to improved security. The daemon process can be restarted
without restarting the entire Apache web server, possibly making
refreshing your codebase more seamless. Consult the mod\_wsgi
documentation to determine which mode is right for your setup. Make
sure you have Apache installed with the mod\_wsgi module activated.
Django will work with any version of Apache that supports mod\_wsgi.

See [How to use Django with mod\_wsgi](/ko/5.1/howto/deployment/wsgi/modwsgi/)
for information on how to configure mod\_wsgi once you have it
installed.

If you can’t use mod\_wsgi for some reason, fear not: Django supports many other
deployment options. One is [uWSGI](/ko/5.1/howto/deployment/wsgi/uwsgi/); it works
very well with [nginx](https://nginx.org/). Additionally, Django follows the WSGI spec
([**PEP 3333**](https://peps.python.org/pep-3333/)), which allows it to run on a variety of server platforms.

## 데이터베이스 구동

Django의 데이터베이스 API 기능을 사용하려면 데이터베이스 서버를 실행해야합니다. Django는 다양한 데이터베이스 서버를 지원하며 공식적으로 [PostgreSQL](https://www.postgresql.org/), [MariaDB](https://mariadb.org/), [MySQL](https://www.mysql.com/), [Oracle](https://www.oracle.com/) 및 SQLite\_가 지원됩니다.

소규모 프로젝트나 프로덕션 환경에 배포할 계획이 없는 프로젝트를 개발하는 경우에는 별도의 서버를 실행할 필요가 없으므로 일반적으로 SQLite가 가장 좋습니다. 그러나 SQLite는 다른 데이터베이스와 많은 차이점이 있으므로 중요한 작업을 하는 경우 프로덕션 환경에서 사용할 계획과 동일한 데이터베이스로 개발하는 것이 좋습니다.

공식적으로 지원되는 데이터베이스 외에도 다른 데이터베이스를 Django와 함께 사용할 수 있도록 해주는:ref:backends provided by 3rd parties 1\`가 있습니다.

To use another database other than SQLite, you’ll need to make sure that the
appropriate Python database bindings are installed:

- PostgreSQL을 사용하는 경우 [psycopg](https://www.psycopg.org/psycopg3/) 또는 [psycopg2](https://www.psycopg.org/) 패키지가 필요합니다. 자세한 내용은 :ref:PostgreSQL notes 를 참조하세요.
- MySQL 또는 MariaDB를 사용하는 경우 mysqlclient\`\`와 같은 :ref:DB API 드라이버\`\`가 필요합니다. 자세한 내용은 MySQL 백엔드에 대한 :ref:주석\`을 참조하세요.
- SQLite를 사용하는 경우 :ref:SQLite backend notes\`를 읽어보시기 바랍니다.
- If you’re using Oracle, you’ll need to install [oracledb](https://oracle.github.io/python-oracledb/), but please read the
  [notes for the Oracle backend](/ko/5.1/ref/databases/#oracle-notes) for details regarding
  supported versions of both Oracle and `oracledb`.
- If you’re using an unofficial 3rd party backend, please consult the
  documentation provided for any additional requirements.

And ensure that the following keys in the `'default'` item of the
[`DATABASES`](/ko/5.1/ref/settings/#std-setting-DATABASES) dictionary match your database connection settings:

- [`ENGINE`](/ko/5.1/ref/settings/#std-setting-DATABASE-ENGINE) – `'django.db.backends.sqlite3'`, `'django.db.backends.postgresql'`, `'django.db.backends.mysql'`, 또는 `'django.db.backends.oracle'`. 그외에 [서드파티 백엔드](/ko/5.1/ref/databases/#third-party-notes) 참조.
- [`NAME`](/ko/5.1/ref/settings/#std-setting-NAME) – The name of your database. If you’re using SQLite, the
  database will be a file on your computer. In that case, `NAME` should be
  the full absolute path, including the filename of that file. You don’t need
  to create anything beforehand; the database file will be created
  automatically when needed. The default value, `BASE_DIR / 'db.sqlite3'`,
  will store the file in your project directory.

> **SQLite 이외의 데이터베이스라면**
>
> SQLite 를 데이터베이스로 사용하지 않는 경우, [`USER`](/ko/5.1/ref/settings/#std-setting-USER), [`PASSWORD`](/ko/5.1/ref/settings/#std-setting-PASSWORD), [`HOST`](/ko/5.1/ref/settings/#std-setting-HOST) 같은 추가 설정이 반드시 필요합니다. 더 자세한 내용은 [`DATABASES`](/ko/5.1/ref/settings/#std-setting-DATABASES) 문서를 참조해 주세요.
>
> Also, make sure that you’ve created the database by this point. Do that
> with “`CREATE DATABASE database_name;`” within your database’s
> interactive prompt.

If you plan to use Django’s `manage.py migrate` command to automatically
create database tables for your models (after first installing Django and
creating a project), you’ll need to ensure that Django has permission to create
and alter tables in the database you’re using; if you plan to manually create
the tables, you can grant Django `SELECT`, `INSERT`, `UPDATE` and
`DELETE` permissions. After creating a database user with these permissions,
you’ll specify the details in your project’s settings file, see
[`DATABASES`](/ko/5.1/ref/settings/#std-setting-DATABASES) for details.

If you’re using Django’s [testing framework](/ko/5.1/topics/testing/) to test
database queries, Django will need permission to create a test database.

## Django 코드 설치

Installation instructions are slightly different depending on whether you’re
installing a distribution-specific package, downloading the latest official
release, or fetching the latest development version.

### Installing an official release with `pip`

This is the recommended way to install Django.

1. Install [pip](https://pip.pypa.io/). The easiest is to use the [standalone pip installer](https://pip.pypa.io/en/latest/installation/). If your
   distribution already has `pip` installed, you might need to update it if
   it’s outdated. If it’s outdated, you’ll know because installation won’t
   work.
2. Take a look at [venv](https://docs.python.org/3/tutorial/venv.html). This tool provides
   isolated Python environments, which are more practical than installing
   packages systemwide. It also allows installing packages without
   administrator privileges. The [contributing tutorial](/ko/5.1/intro/contributing/) walks through how to create a virtual environment.
3. After you’ve created and activated a virtual environment, enter the command:

   ```console
   $ python -m pip install Django
   ```

   *Windows*

   ```doscon
   ...\> py -m pip install Django
   ```

### Installing a distribution-specific package

Check the [distribution specific notes](/ko/5.1/misc/distributions/) to see if
your platform/distribution provides official Django packages/installers.
Distribution-provided packages will typically allow for automatic installation
of dependencies and supported upgrade paths; however, these packages will rarely
contain the latest release of Django.

### Installing the development version

> **Tracking Django development**
>
> If you decide to use the latest development version of Django,
> you’ll want to pay close attention to [the development timeline](https://code.djangoproject.com/timeline),
> and you’ll want to keep an eye on the [release notes for the
> upcoming release](/ko/5.1/releases/#development-release-notes). This will help you stay
> on top of any new features you might want to use, as well as any changes
> you’ll need to make to your code when updating your copy of Django.
> (For stable releases, any necessary changes are documented in the
> release notes.)

If you’d like to be able to update your Django code occasionally with the
latest bug fixes and improvements, follow these instructions:

1. Make sure that you have [Git](https://git-scm.com/) installed and that you can run its commands
   from a shell. (Enter `git help` at a shell prompt to test this.)
2. Check out Django’s main development branch like so:

   ```console
   $ git clone https://github.com/django/django.git
   ```

   *Windows*

   ```doscon
   ...\> git clone https://github.com/django/django.git
   ```

   This will create a directory `django` in your current directory.
3. Make sure that the Python interpreter can load Django’s code. The most
   convenient way to do this is to use a virtual environment and [pip](https://pip.pypa.io/). The
   [contributing tutorial](/ko/5.1/intro/contributing/) walks through how to
   create a virtual environment.
4. After setting up and activating the virtual environment, run the following
   command:

   ```console
   $ python -m pip install -e django/
   ```

   *Windows*

   ```doscon
   ...\> py -m pip install -e django\
   ```

   This will make Django’s code importable, and will also make the
   `django-admin` utility command available. In other words, you’re all
   set!

When you want to update your copy of the Django source code, run the command
`git pull` from within the `django` directory. When you do this, Git will
download any changes.