emreberber/nginx-notes

Nginx Notes

my nginx notes on ubuntu server

📝 Table of Contents

What is Nginx ?
Installing
Commands
Contexts
The Main Nginx Configuration File
Editing nginx.conf
Create Your Site(s) Directory Structure
Nginx Server Blocks
MariaDB
Installing WPCLI on Your Server
Wordpress Installing a Wordpress Site Using WP-CLI
Author
Useful Links

🧐 What is Nginx ?

NGINX is open source software for web serving, reverse proxying, caching, load balancing, media streaming, and more. It started out as a web server designed for maximum performance and stability. In addition to its HTTP server capabilities, NGINX can also function as a proxy server for email (IMAP, POP3, and SMTP) and a reverse proxy and load balancer for HTTP, TCP, and UDP servers.

🏁 Installing

$ sudo apt install nginx

🚀 Commands

# edit nginx.conf
$ sudo vi /etc/nginx/nginx.conf


# determine number of cpu cores
$ lscpu


# determine number of worker connections
$ ulimit -n


# test nginx configuration file syntax before reload
$ sudo nginx -t


# reload / restart nginx
$ sudo systemctl reload nginx OR restart nginx

Context

Main Context

worker_procesess
worker_rlimit_nofile

Events Context

worker_connections 1024;
multi_accept on;
use epoll;

HTTP Context

server_tokens off;
server_names_hash_bucket_size 64;
access_log off;
access_log /var/log/nginx/access.log
gzip on;
buffers, timeouts & filehandle caching

Buffers

client_body_buffer_size 10k;
client_header_buffer_size 1k;
client_max_body_size 8m;
large_client_header_buffers 2 1k;

Timeouts

client_body_timeout 3m;
client_header_timeout 3m;
keepalive_timeout 100;
send_timeout 3m;

Filehandle Caching

open_file_cache max=1000 inactive 20s;
open_file_cache_valid 30s;
open_file_cache_min_uses 5;
open_file_cache_errors off;

The Main Nginx Configuration File

For many distributions, the file will be located at /etc/nginx/nginx.conf. If it does not exist there, it may also be at /usr/local/nginx/conf/nginx.conf or /usr/local/etc/nginx/nginx.conf

$ cd /etc/nginx
$ sudo cp nginx.conf nginx.conf.$(date +%Y-%m-%d)
$ lscpu
...
CPU(s):              1
...


$ ulimit -n
1024


$ sudo vi nginx.conf

Editing nginx.conf

user www-data;
worker_processes auto;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;


to


user www-data;
worker_processes 1;
worker_rlimit_nofile 10000;
pid /run/nginx.pid;
include /etc/nginx/modules-enabled/*.conf;

www-data is the user that web servers on Ubuntu (Apache, Nginx) use by default for normal operation. The web server process can access any file that www-data can access. (su www-data)
worker_processes is amount of cores you have on your setup. Some last versions calculate it automatically, use auto;
worker_rlimit_nofile is the maximum file descriptors that can be opened by each worker process.

events {
        worker_connections 768;
        # multi_accept on;
}


to


events {
        worker_connections 1024;
        multi_accept on;
        use epoll;
}

events context is provides the configuration file context in which the directives that affect connection processing are specified.
worker_conections command tells our worker processes how many people can simultaneously be served by Nginx. unlimit -n command gives 1024.
use epoll is optimized to serve many clients with each thread, essential for linux.
multi_accept on accept as many connections as possible, may flood worker connections if set too low.
Why is 'multi_accept' 'off' as default in Nginx? Probably because with on, all the worker processes are active and try to handle all of the incoming request simultaneously. When disabled, Nginx decides which child process gets to deal with the request one by one. As Nginx is very efficient at this, this probably serves most people well. Some consider it a risk to enable it, as it may flood the worker connections with requests.

http {


        ##
        # Basic Settings
        ##


        sendfile on;
        tcp_nopush on;
        tcp_nodelay on;
        # keepalive_timeout 65;
        types_hash_max_size 2048;
        # server_tokens off;


        # server_names_hash_bucket_size 64;
        # server_name_in_redirect off;


        include /etc/nginx/mime.types;
        default_type application/octet-stream;
        ...


to


http {


        ##
        # Basic Settings
        ##


        sendfile on;
        tcp_nopush on;
        tcp_nodelay on;
        keepalive_timeout 65;
        types_hash_max_size 2048;
        server_tokens off;


        # server_names_hash_bucket_size 64;
        # server_name_in_redirect off;


        include /etc/nginx/mime.types;
        default_type application/octet-stream;
        ...

http context is when configuring Nginx as a web server or reverse proxy, the "http" context will hold the majority of the configuration. This context will contain all of the directives and other contexts necessary to define how the program will handle HTTP or HTTPS connections. The http context is a sibling of the events context, so they should be listed side-by-side, rather than nested. They both are children of the main context.
sendfile by default, NGINX handles file transmission itself and copies the file into the buffer before sending it. Enabling the sendfile directive eliminates the step of copying the data into the buffer and enables direct copying data from one file descriptor to another. Alternatively, to prevent one fast connection from entirely occupying the worker process, you can use the sendfile_max_chunk directive to limit the amount of data transferred in a single sendfile() call (in this example, to 1 MB): sendfile on; sendfile_mac_chunk 1m;
tcp_nopush directive together with the sendfile on;directive. This enables NGINX to send HTTP response headers in one packet right after the chunk of data has been obtained by sendfile().
tcp_nodelay directive allows override of Nagle’s algorithm, originally designed to solve problems with small packets in slow networks. The algorithm consolidates a number of small packets into a larger one and sends the packet with a 200 ms delay. Nowadays, when serving large static files, the data can be sent immediately regardless of the packet size. The delay also affects online applications (ssh, online games, online trading, and so on). By default, the tcp_nodelay directive is set to on which means that the Nagle’s algorithm is disabled. Use this directive only for keepalive connections
tcp_nodelay on;
keepalive_timeout 65;

Create Your Site(s) Directory Structure

wpcli.com
ww.wpcli.com
blog.wpcli.com
forum.wpcli.com

server web root /var/www
ownership root:root
create directories site.com/public_html
using tree to view directory layout

Commands

changing ownership
$ chown -R user:group /path
create directory
$ mkdir
create directory with sub-directories
$ mkdir -p
install tree
$ sudo apt install tree

Implementation Steps

$ cd /var/www
$ ls -l
total 4
drwxr-xr-x 2 root root 4096 Jun  3 17:31 html
$  sudo chown -R emre:emre /var/www/
$ ls -l
total 4
drwxr-xr-x 2 emre emre 4096 Jun  3 17:31 html
$ mkdir wpcli.com
html  wpcli.com
$ cd wpcli.com/
$ mkdir public_html
$ ls
public_html
$ cd ..
$ mkdir -p www.wpcli.com/public_html
$ mkdir -p blog.wpcli.com/public_html
$ mkdir -p forum.wpcli.com/public_html
$ ls
blog.wpcli.com  forum.wpcli.com  html  wpcli.com  www.wpcli.com
$ sudo apt install tree
$ tree
.
├── blog.wpcli.com
│   └── public_html
├── forum.wpcli.com
│   └── public_html
├── html
│   └── index.nginx-debian.html
├── wpcli.com
│   └── public_html
└── www.wpcli.com
    └── public_html

Nginx Server Blocks

Configuration files : /etc/nginx/sites-available

Commands

# create backup copy of default file
$ sudo cp default default.bak

# path to php7.0-fpm.sock
$ sudo find / -name php7.0-fpm.sock

# test nginx conf file syntax before reload
$ sudo nginx -t

# reload nginx
$ sudo systemctl reload nginx

Implementation Steps

$ cd /etc/nginx/sites-available
$ ls
default
$ sudo cp default default.bak
$ sudo vi default

default file

server {
        listen 80 default_server;
        listen [::]:80 default_server;

        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;

        server_name _;

        location / {
                try_files $uri $uri/ =404;
        }

        location ~ \.php$ {
                include snippets/fastcgi-php.conf;

                # With php-fpm (or other unix sockets):
                fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
        }
}

$ sudo nginx -t 
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

control .sock file

$ ls /var/run/php/php7.2-fpm.sock

and change php version 7.0 to 7.2

location ~ \.php$ {
                include snippets/fastcgi-php.conf;

                # With php-fpm (or other unix sockets):
                fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
        }

Nginx Location Modifiers

= exact match
^~ preferential prefix match
~ and ~* regex match

Exact Match Example

location = /favicon.ico {
        expires 1y;
}
http://www.site.com/favicon.ico

Preferential Example

Preferential prefix

location ^~ /.well-known {
        try_files $uri = 404;
}
http://www.site.com/.well-known

Case Insensitive Regex

location ~* /uploads/.*\.php$ {
        deny all;
}

default : /etc/nginx/sites-available/default
domain : /etc/nginx/sites-available/domain

$ sudo cp default wpcli.com
$ ls
default  default.bak  wpcli.com
$ sudo vi wpcli.com

server {
        listen 80;
        listen [::]:80;

        root /var/www/wpcli.com/public_html;

        # Add index.php to the list if you are using PHP
        index index.php;

        server_name wpcli.com www.wpcli.com; # or ip

        location / {
                try_files $uri $uri/ /index.php$args;
        }

        location ~ \.php$ {
                include snippets/fastcgi-php.conf;

                # With php-fpm (or other unix sockets):
                fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
        }
}

$ sudo nginx -t
$ sudo ln -s /etc/nginx/sites-available/wpcli.com /etc/nginx/sites-enabled/wpcli.com

$ cd /etc/nginx/sites-enabled/
$ ls
default wpcli.com

$ sudo systemctl restart nginx

and the view your browser, http://www.wpcli.com

MariaDB

login into MariaDB
create the database
create a database user
give that user privilege on the database
flush privileges - refresh database

Commands

login into database
$ sudo mysql -u root

show all databases
> show databases;

create a database
> create database db_name;

create a user
> create user db_username;

granting privileges
> grant all privileges on db_name.* to 'db_user'@'localhost' identified by 'password';

flush privileges
> flush privileges;

show user's privileges
> show grants for 'db_username'@'localhost';

delete a database
> drop database db_name;

delete a database user
> drop user db_user;

exit MariaDB
> exit

Implementation Steps

db : wpdb
user : wpemre
pass : wppass

$ sudo mysql -u root
MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
+--------------------+

MariaDB [(none)]> create database  wpdb;
Query OK, 1 row affected (0.01 sec)

MariaDB [(none)]> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| wpdb               |
+--------------------+
4 rows in set (0.00 sec)

MariaDB [(none)]> create user wpemre;
Query OK, 0 rows affected (0.00 sec)

MariaDB [(none)]> grant all privileges on wpdb .* to 'wpemre'@'localhost' identified by 'wppass';

MariaDB [(none)]> flush privileges;
Query OK, 0 rows affected (0.00 sec)

MariaDB [(none)]> show grants for 'wpemre'@'localhost';
+---------------------------------------------------------------------------------------------------------------+
| Grants for wpemre@localhost                                                                                   |
+---------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'wpemre'@'localhost' IDENTIFIED BY PASSWORD '*C9B2DB1CA193280B971CA3602D5174A5D637D2BF' |
| GRANT ALL PRIVILEGES ON `wpdb`.* TO 'wpemre'@'localhost'                                                      |
+---------------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)

MariaDB [(none)]> exit
Bye

Installing WPCLI on Your Server

$ curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
$ chmod +x wp-cli.phar
$ sudo mv wp-cli.phar /usr/local/bin/wp
$ wp --info

Implementation Steps

$ curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.pha
$ ls
wp-cli.phar

$ ls -l
-rw-rw-r-- 1 emre emre 5506663 Jul  7 18:48 wp-cli.phar

$ chmod +x wp-cli.phar
$ ls -l
-rwxrwxr-x 1 emre emre 5506663 Jul  7 18:48 wp-cli.phar

$ sudo mv wp-cli.phar /usr/local/bin/wp
$ wp --info
OS:     Linux 4.15.0-1033-gcp #35-Ubuntu SMP Fri May 17 13:27:54 UTC 2019 x86_64
Shell:  /bin/bash
PHP binary:     /usr/bin/php7.2
PHP version:    7.2.19-0ubuntu0.18.04.1
php.ini used:   /etc/php/7.2/cli/php.ini
WP-CLI root dir:        phar://wp-cli.phar/vendor/wp-cli/wp-cli
WP-CLI vendor dir:      phar://wp-cli.phar/vendor
WP_CLI phar path:       /home/emre
WP-CLI packages dir:
WP-CLI global config:
WP-CLI project config:
WP-CLI version: 2.2.0

Wordpress Installing a Wordpress Site Using WP-CLI

Commands

download wordpress
$ wp core download

create he wp-config.php file
$ wp core config --dbname= --dbuser= --dbpass= --dbprefix=

!!! Do Not Use wp_ as the Wordpress Database Prefix !!!

installing wordpress
$ wp core install --url= --title= --admin_user= --admin_password= --admin_email=

Implementation Steps

$ cd /var/www
$ ls
blog.wpcli.com  forum.wpcli.com  html  wpcli.com  www.wpcli.com
$ cd wpcli.com/public_html
$ wp core download
Downloading WordPress 5.2.2 (en_US)...
md5 hash verified: aea5bb5e4fd51034f67c85e6d8bc6bbf
Success: WordPress downloaded.

$ wp core config --dbname=wpdb --dbuser=wpemre --dbpass=wppass --dbprefix=4Hx_ --locale=tr_TR
Success: Generated 'wp-config.php' file.

$ wp core install --url=http://www.wpcli.com --title='WP cli' --admin_user=admin_emre --admin_password=admin_pass --admin_email=admin@wpcli.com
(i change wpcli.com to http://35.236.64.179)
sh: 1: /usr/sbin/sendmail: not found
Success: WordPress installed successfully

$ sudo apt update && sudo apt install sendmail

$ cd /etc/nginx/sites-available
$ sudo vi wpcli.com
server_name 35.236.64.179;
$ sudo nginx -t
$ sudo systemctl restart nginx

and then view browser 35.236.64.179
for admin panel -> 35.236.64.179/wp-admin

emreberber / nginx-notes

Nginx Notes

📝 Table of Contents

🧐 What is Nginx ?

🏁 Installing

🚀 Commands

Context

The Main Nginx Configuration File

Editing nginx.conf

Create Your Site(s) Directory Structure

Commands

Implementation Steps

Nginx Server Blocks

Commands

Implementation Steps

Nginx Location Modifiers

MariaDB

Commands

Implementation Steps

Installing WPCLI on Your Server

Implementation Steps

Wordpress Installing a Wordpress Site Using WP-CLI

Commands

Implementation Steps

✍️ Author

🎉 Useful Links

About