이 문서는 Django를 설치하는 방법을 설명합니다.
\nDjango는 Python 웹 프래임워크 입니다. 장고와 어떤 파이썬 버전을 사용해야 하나요? 에서 자세한 내용을 참고하세요.
\n최신 Python 버전은 https://www.python.org/downloads/ 또는 운영 체제 패키지 관리자에게 문의하십시오.
\n\n\nmod_wsgi 설치Link to this heading#단지 Django를 테스트하고 싶은것 이라면 다음 섹션으로 건너 뛰어도 괜찮습니다. Django는 테스트를 위한 경량의 웹서버를 포함하고 있기때문에 프로덕션 환경에 Django를 배포할 준비가 될때까지 아파치를 설정할 필요는 없습니다.
\n실제 서비스 환경의 사이트에서 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에서도 작동합니다.
\nSee How to use Django with mod_wsgi\nfor information on how to configure mod_wsgi once you have it\ninstalled.
\nIf you can’t use mod_wsgi for some reason, fear not: Django supports many other\ndeployment options. One is uWSGI; it works\nvery well with nginx. Additionally, Django follows the WSGI spec\n(PEP 3333), which allows it to run on a variety of server platforms.
\nIf you plan to use Django’s database API functionality, you’ll need to make\nsure a database server is running. Django supports many different database\nservers and is officially supported with PostgreSQL, MySQL, Oracle and\nSQLite.
\nIf you are developing a simple project or something you don’t plan to deploy\nin a production environment, SQLite is generally the simplest option as it\ndoesn’t require running a separate server. However, SQLite has many differences\nfrom other databases, so if you are working on something substantial, it’s\nrecommended to develop with the same database that you plan on using in\nproduction.
\nIn addition to the officially supported databases, there are backends\nprovided by 3rd parties that allow you to use other\ndatabases with Django.
\nIn addition to a database backend, you’ll need to make sure your Python\ndatabase bindings are installed.
\nIf you’re using PostgreSQL, you’ll need the psycopg2 package. Refer to the\nPostgreSQL notes for further details.
If you’re using MySQL, you’ll need a DB API driver like mysqlclient. See notes for the MySQL\nbackend for details.
If you’re using SQLite you might want to read the SQLite backend notes.
If you’re using Oracle, you’ll need a copy of cx_Oracle, but please\nread the notes for the Oracle backend for details\nregarding supported versions of both Oracle and cx_Oracle.
If you’re using an unofficial 3rd party backend, please consult the\ndocumentation provided for any additional requirements.
If you plan to use Django’s manage.py migrate command to automatically\ncreate database tables for your models (after first installing Django and\ncreating a project), you’ll need to ensure that Django has permission to create\nand alter tables in the database you’re using; if you plan to manually create\nthe tables, you can simply grant Django SELECT, INSERT, UPDATE and\nDELETE permissions. After creating a database user with these\npermissions, you’ll specify the details in your project’s settings file,\nsee DATABASES for details.
If you’re using Django’s testing framework to test\ndatabase queries, Django will need permission to create a test database.
\nInstallation instructions are slightly different depending on whether you’re\ninstalling a distribution-specific package, downloading the latest official\nrelease, or fetching the latest development version.
\nIt’s easy, no matter which way you choose.
\npipLink to this heading#This is the recommended way to install Django.
\nInstall pip. The easiest is to use the standalone pip installer. If your\ndistribution already has pip installed, you might need to update it if\nit’s outdated. If it’s outdated, you’ll know because installation won’t\nwork.
Take a look at virtualenv and virtualenvwrapper. These tools provide\nisolated Python environments, which are more practical than installing\npackages systemwide. They also allow installing packages without\nadministrator privileges. The contributing tutorial walks through how to create a virtualenv.
After you’ve created and activated a virtual environment, enter the command:
\nLinux / macOS
$ pip install Django\nWindows
...\\> pip install Django\nCheck the distribution specific notes to see if\nyour platform/distribution provides official Django packages/installers.\nDistribution-provided packages will typically allow for automatic installation\nof dependencies and easy upgrade paths; however, these packages will rarely\ncontain the latest release of Django.
\nIf you’d like to be able to update your Django code occasionally with the\nlatest bug fixes and improvements, follow these instructions:
\nMake sure that you have Git installed and that you can run its commands\nfrom a shell. (Enter git help at a shell prompt to test this.)
Check out Django’s main development branch like so:
\nLinux / macOS
$ git clone https://github.com/django/django.git\nWindows
...\\> git clone https://github.com/django/django.git\nThis will create a directory django in your current directory.
Make sure that the Python interpreter can load Django’s code. The most\nconvenient way to do this is to use virtualenv, virtualenvwrapper, and\npip. The contributing tutorial walks through\nhow to create a virtualenv.
After setting up and activating the virtualenv, run the following command:
\nLinux / macOS
$ pip install -e django/\nWindows
...\\> pip install -e django\\\nThis will make Django’s code importable, and will also make the\ndjango-admin utility command available. In other words, you’re all\nset!
When you want to update your copy of the Django source code, just run the\ncommand git pull from within the django directory. When you do this,\nGit will automatically download any changes.