How to deploy Django through Nginx based on ubuntu

1. Install nginx Nginx is a lightweight web server/reverse proxy server and email (imap/pop3) proxy server , and released under a bsd-like license. Its characteristics are that it occupies less memory and has strong concurrency capabilities. In fact, nginx's concurrency capabilities do perform better among web servers of the same type.

nginx is also a very popular web server. We will also give a brief introduction here to use it to deploy django.

nginx official website:

Open the ubuntu console (ctrl alt t) and use the ubuntu warehouse to install.

fnngj@ubuntu:~$ sudo apt-get install nginx #安装

Start nginx:

fnngj@ubuntu:~$ /etc/init.d/nginx start #启动
fnngj@ubuntu:~$ /etc/init.d/nginx stop #关闭
fnngj@ubuntu:~$ /etc/init.d/nginx restart #重启

Modify the nginx default port number, open the /etc/nginx/nginx.conf file, and modify the port number.

 server {
  listen    8088;  # 修改端口号
  server_name localhost;

  #charset koi8-r; 

  #access_log logs/host.access.log main;

  location / {
    root  html;
    index index.html index.htm;
  }

Approximately at line 36 of the file, change the default port number 80 to another port number, such as 8088. Because the default port number 80 is easily occupied by other applications.

Then, restart nginx through the above command. Visit: http://127.0.0.1:8088/

　

If the above picture appears, it means nginx started successfully.

2. Install uwsgi

Install uwsgi through pip.

root@ubuntu:/etc# python3 -m pip install uwsgi

Test uwsgi, create the test.py file:

def application(env, start_response):
  start_response('200 ok', [('content-type','text/html')])
  return [b"hello world"]

Run the file through uwsgi.

fnngj@ubuntu:~/pydj$ uwsgi --http :8001 --wsgi-file test.py

Next configure the connection between django and uwsgi. Here, the assumed location of my django project is: /home/fnngj/pydj/myweb

Copy code The code is as follows:

uwsgi --http :8001 --chdir / home/fnngj/pydj/myweb/ --wsgi-file myweb/wsgi.py --master --processes 4 --threads 2 --stats 127.0.0.1:9191

Commonly used Options:

http: Protocol type and port number

processes: Number of processes started

workers: Number of processes started, equivalent to processes (according to the official website) is spawn the specified number of workers / processes)

chdir: Specify the running directory (chdir to specified directory before apps loading)

wsgi-file: Load wsgi-file (load .wsgi file)

stats: Enable the stats server on the specified address.

threads: Run threads. Due to the existence of gil, I think this is really useless. (run each worker in prethreaded mode with the specified number of threads)

master: Allow the master process to exist (enable master process)

daemonize: Make the process run in the background and log to Specified log file or udp server (daemonize uwsgi). In fact, the most commonly used method is to output the running records to a local file.

pidfile: Specify the location of the pid file and record the pid number of the main process.

vacuum: Automatically clean up the environment when the server exits, delete the unix socket file and pid file (try to remove all of the generated file/sockets)

3. nginx uwsgi django

                                                                                                                                                                                                                                                                                       

Next, we have to combine the three. First, list the files required for the project:

myweb/

├── manage.py

├── myweb/

│  ├── __init__.py

│  ├── settings.py

│  ├── urls.py

│  └── wsgi.py

└── myweb_uwsgi.ini

When we created the myweb project through django, the wsgi.py file was generated for us in the subdirectory myweb. Therefore, we only need to create the myweb_uwsgi.ini configuration file. Of course, uwsgi supports multiple types of configuration files, such as xml, ini, etc. Here, use ini type configuration.

# myweb_uwsgi.ini file
[uwsgi]

# django-related settings

socket = :8000

# the base directory (full path)
chdir      = /home/fnngj/pydj/myweb

# django s wsgi file
module     = myweb.wsgi

# process-related settings
# master
master     = true

# maximum number of worker processes
processes    = 4

# ... with appropriate permissions - may be needed
# chmod-socket  = 664
# clear environment on exit
vacuum     = true

This configuration is actually equivalent to documenting it through the wsgi command followed by a bunch of parameters in the previous section.

socket Specifies the port number for project execution.

chdir specifies the directory of the project.

module myweb.wsgi can be understood in this way. For the myweb_uwsgi.ini file, there is a myweb directory at the same level as it, and there is a wsgi.py file in this directory.

For other parameters, please refer to the introduction of parameters in the previous section.

接下来，切换到myweb项目目录下，通过uwsgi命令读取myweb_uwsgi.ini文件启动项目。

fnngj@ubuntu:~$ cd /home/fnngj/pydj/myweb/
fnngj@ubuntu:~/pydj/myweb$ uwsgi --ini myweb_uwsgi.ini 
[uwsgi] getting ini configuration from myweb_uwsgi.ini
*** starting uwsgi 2.0.12 (32bit) on [sat mar 12 13:05:06 2016] ***
compiled with version: 4.8.4 on 26 january 2016 06:14:41
os: linux-3.19.0-25-generic #26~14.04.1-ubuntu smp fri jul 24 21:18:00 utc 2015
nodename: ubuntu
machine: i686
clock source: unix
detected number of cpu cores: 2
current working directory: /home/fnngj/pydj/myweb
detected binary path: /usr/local/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
chdir() to /home/fnngj/pydj/myweb
your processes number limit is 15962
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to tcp address :8000 fd 3
python version: 3.4.3 (default, oct 14 2015, 20:37:06) [gcc 4.8.4]
*** python threads support is disabled. you can enable it with --enable-threads ***
python main interpreter initialized at 0x8b52dc0
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 319920 bytes (312 kb) for 4 cores
*** operational mode: preforking ***
wsgi app 0 (mountpoint='') ready in 1 seconds on interpreter 0x8b52dc0 pid: 7158 (default app)
*** uwsgi is running in multiple interpreter mode ***
spawned uwsgi master process (pid: 7158)
spawned uwsgi worker 1 (pid: 7160, cores: 1)
spawned uwsgi worker 2 (pid: 7161, cores: 1)
spawned uwsgi worker 3 (pid: 7162, cores: 1)
spawned uwsgi worker 4 (pid: 7163, cores: 1)

注意查看uwsgi的启动信息，如果有错，就要检查配置文件的参数是否设置有误。

再接下来要做的就是修改nginx.conf配置文件。打开/etc/nginx/nginx.conf文件，添加如下内容。

……
server {
  listen     8099; 
  server_name  127.0.0.1 
  charset utf-8;
  access_log   /var/log/nginx/myweb_access.log;
  error_log    /var/log/nginx/myweb_error.log;

  client_max_body_size 75m;

  location / { 
    include uwsgi_params;
    uwsgi_pass 127.0.0.1:8000;
    uwsgi_read_timeout 2;
  }  
  location /static {
    expires 30d;
    autoindex on; 
    add_header cache-control private;
    alias /home/fnngj/pydj/myweb/static/;
   }
 }
……

 listen 指定的是nginx代理uwsgi对外的端口号。

server_name  网上大多资料都是设置的一个网址（例，www.example.com），我这里如果设置成网址无法访问，所以，指定的到了本机默认ip。

在进行配置的时候，我有个问题一直想不通。nginx到底是如何uwsgi产生关联。现在看来大概最主要的就是这两行配置。

include uwsgi_params;

uwsgi_pass 127.0.0.1:8000;

include 必须指定为uwsgi_params；而uwsgi_pass指的本机ip的端口与myweb_uwsgi.ini配置文件中的必须一直。

现在重新启动nginx，翻看上面重启动nginx的命令。然后，访问：http://127.0.0.1:8099/

通过这个ip和端口号的指向，请求应该是先到nginx的。如果你在页面上执行一些请求，就会看到，这些请求最终会转到uwsgi来处理。

The above is the detailed content of How to deploy Django through Nginx based on ubuntu. For more information, please follow other related articles on the PHP Chinese website!