이 문서는 Django를 설치하는 방법을 설명합니다.
Django는 Python 웹 프래임워크 입니다. 장고와 어떤 파이썬 버전을 사용해야 하나요? 에서 자세한 내용을 참고하세요.
최신 Python 버전은 https://www.python.org/downloads/ 또는 운영 체제 패키지 관리자에게 문의하십시오.
Jython 환경의 Django
Jython (Java 플랫폼을 위해 구현된 Python) 은 Python 3와 호환되지 않기 때문에 Django 버전 2.0이상을 Jython에서 실행할 수 없습니다.
Windows 환경의 Python
만약 Windows를 사용하여 Django를 시작하고 싶다면, :doc:`/howto/windows`를 참고하세요.
mod_wsgi
설치¶단지 Django를 테스트하고 싶은것 이라면 다음 섹션으로 건너 뛰어도 괜찮습니다. Django는 테스트를 위한 경량의 웹서버를 포함하고 있기때문에 프로덕션 환경에 Django를 배포할 준비가 될때까지 아파치를 설정할 필요는 없습니다.
실제 서비스 환경의 사이트에서 Django를 사용하려면, Apache 와 `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 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; it works very well with nginx. Additionally, Django follows the WSGI spec (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, MySQL, Oracle and SQLite.
If you are developing a simple project or something you don't plan to deploy in a production environment, SQLite is generally the simplest 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 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.
mysqlclient
. See notes for the MySQL
backend for details.cx_Oracle
.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 simply 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
for details.
If you're using Django's testing framework to test database queries, Django will need permission to create a test database.
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.
It's easy, no matter which way you choose.
pip
¶This is the recommended way to install Django.
Install pip. The easiest is to use the standalone pip installer. 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.
Take a look at virtualenv and virtualenvwrapper. These tools provide isolated Python environments, which are more practical than installing packages systemwide. They also allow installing packages without administrator privileges. The contributing tutorial walks through how to create a virtualenv.
After you've created and activated a virtual environment, enter the command:
$ pip install Django
...\> pip install Django
Check the distribution specific notes to see if your platform/distribution provides official Django packages/installers. Distribution-provided packages will typically allow for automatic installation of dependencies and easy upgrade paths; however, these packages will rarely contain the latest release of Django.
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, and you'll want to keep an eye on the release notes for the upcoming release. 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:
Make sure that you have Git installed and that you can run its commands
from a shell. (Enter git help
at a shell prompt to test this.)
Check out Django's main development branch like so:
$ git clone https://github.com/django/django.git
...\> git clone https://github.com/django/django.git
This will create a directory django
in your current directory.
Make sure that the Python interpreter can load Django's code. The most convenient way to do this is to use virtualenv, virtualenvwrapper, and pip. The contributing tutorial walks through how to create a virtualenv.
After setting up and activating the virtualenv, run the following command:
$ pip install -e django/
...\> 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, just run the
command git pull
from within the django
directory. When you do this,
Git will automatically download any changes.
12월 02, 2019