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

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

## Python 설치

Django는 Python 웹 프래임워크 입니다. [장고와 어떤 파이썬 버전을 사용해야 하나요?](/ko/3.0/faq/install/#faq-python-version-support) 에서 자세한 내용을 참고하세요.

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

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

## Apache와 `mod_wsgi` 설치

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

실제 서비스 환경의 사이트에서 Django를 사용하려면, [Apache](https://httpd.apache.org/) 와 mod\_wsgi\`\_를 사용하세요. mod\_wsgi는 임베이디드 모드와 데몬 모드 중 하나로 운영할수 있습니다. 임베이디드 모드에서 mod\_wsgi는 mod\_perl과 비슷합니다 – 이 모드에서는 Apache 안에 Python을 삽입하고 서버가 시작될때 Python 코드를 메모리에 로드합니다. 아파치 프로세스가 실행되는 동안 코드가 메모리에 남아 있기때문에 다른 서버 구성보다 성능이 크게 향상됩니다. 데몬모드 에서 mod\_wsgi는 요청을 처리하는 독립적인 데몬 프로세스를 생성합니다. 데몬 프로세스는 웹 서버와 다른 사용자로 실행할 수 있고 이는 보안을 향상할 수 있습니다. 데몬 프로세스는 Apache 웹서버를 재시작하지 않고도 다시시작 할 수 있기 때문에 보다 원할하게 코드베이스를 수정 할 수 있습니다. 여러분의 구성에 맞는 모드를 확인 하려면 mod\_wsgi 문서를 참조하세요. mod\_wsgi 모듈이 활성화 된 상태로 Apache가 설치되어있는지 확인하세요. Django는 mod\_wsgi를 지원하는 어떤 버전의 Apache에서도 작동합니다.

See [How to use Django with mod\_wsgi](/ko/3.0/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/3.0/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.

## 데이터베이스 구동

If you plan to use Django’s database API functionality, you’ll need to make
sure a database server is running. Django supports many different database
servers and is officially supported with [PostgreSQL](https://www.postgresql.org/), [MariaDB](https://mariadb.org/), [MySQL](https://www.mysql.com/), [Oracle](https://www.oracle.com/)
and [SQLite](https://www.sqlite.org/).

If you are developing a small project or something you don’t plan to deploy in
a production environment, SQLite is generally the best option as it doesn’t
require running a separate server. However, SQLite has many differences from
other databases, so if you are working on something substantial, it’s
recommended to develop with the same database that you plan on using in
production.

In addition to the officially supported databases, there are [backends
provided by 3rd parties](/ko/3.0/ref/databases/#third-party-notes) that allow you to use other
databases with Django.

In addition to a database backend, you’ll need to make sure your Python
database bindings are installed.

- If you’re using PostgreSQL, you’ll need the [psycopg2](https://www.psycopg.org/) package. Refer to the
  [PostgreSQL notes](/ko/3.0/ref/databases/#postgresql-notes) for further details.
- If you’re using MySQL or MariaDB, you’ll need a [DB API driver](/ko/3.0/ref/databases/#mysql-db-api-drivers) like `mysqlclient`. See [notes for the MySQL
  backend](/ko/3.0/ref/databases/#mysql-notes) for details.
- If you’re using SQLite you might want to read the [SQLite backend notes](/ko/3.0/ref/databases/#sqlite-notes).
- If you’re using Oracle, you’ll need a copy of [cx\_Oracle](https://oracle.github.io/python-cx_Oracle/), but please
  read the [notes for the Oracle backend](/ko/3.0/ref/databases/#oracle-notes) for details
  regarding supported versions of both Oracle and `cx_Oracle`.
- If you’re using an unofficial 3rd party backend, please consult the
  documentation provided for any additional requirements.

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/3.0/ref/settings/#std-setting-DATABASES) for details.

If you’re using Django’s [testing framework](/ko/3.0/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/installing/#installing-with-get-pip-py). 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/3.0/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/3.0/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/3.0/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/3.0/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.