This repository contains the Nginx configurations used within the series Hosting WordPress Yourself. It contains best practices from various sources, including the WordPress Codex and H5BP. The following example sites are included:

• singlesite.com - WordPress single site install (no SSL or page caching)
• ssl.com - WordPress on HTTPS
• fastcgi-cache.com - WordPress with FastCGI caching
• ssl-fastcgi-cache.com - WordPress on HTTPS with FastCGI caching
• multisite-subdomain.com - WordPress Multisite install using subdomains
• multisite-subdirectory.com - WordPress Multisite install using subdirectories

Looking for a modern hosting environment provisioned using Ansible? Check out WordPress Ansible.

The php-fpm pool configuration is located in global/php-pool.conf and defaults to PHP 7.1. It will need modified if you want the default php-fpm pool service to be a different PHP version. Additional PHP version upstream definitions can be added to the /upstreams folder (a PHP 7.0 sample is provided there). You can either use the default pool using $upstream in your nginx configurations or the specific upstream definition (i.e. php71, php70) setup by your custom upstream definitions.

For example, currently the nginx configuration for singlesite.com has the following set for php requests:

fastcgi_pass    $upstream

You could change that to the following to use the php 7.0 php service instead (assuming that php7.0-fpm service is running).

fastcgi_pass    php70

This effectively allows you to have different server blocks execute different versions of PHP if needed.

You can use these sample configurations as reference or directly by replacing your existing nginx directory. Follow the steps below to replace your existing nginx configuration.

Backup any existing config:

sudo mv /etc/nginx /etc/nginx.backup

Clone the repo:

sudo git clone https://github.com/A5hleyRich/wordpress-nginx.git /etc/nginx

Symlink the default file from sites-available to sites-enabled, which will setup a catch-all server block. This will ensure unrecognised domains return a 444 response.

sudo ln -s /etc/nginx/sites-available/default /etc/nginx/sites-enabled/default

Copy one of the example configurations from sites-available to sites-available/yourdomain.com:

sudo cp /etc/nginx/sites-available/singlesite.com /etc/nginx/sites-available/yourdomain.com

Edit the site accordingly, paying close attention to the server name and paths.

To enable the site, symlink the configuration into the sites-enabled directory:

sudo ln -s /etc/nginx/sites-available/yourdomain.com /etc/nginx/sites-enabled/yourdomain.com

Test the configuration:

sudo nginx -t

If the configuration passes, restart Nginx:

sudo /etc/init.d/nginx reload

This repository has the following structure, which is based on the conventions used by a default Nginx install on Debian:

.
├── conf.d
├── global
    └── server
├── sites-available
├── sites-enabled

conf.d - configurations for additional modules.

global - configurations within the http block.

global/server - configurations within the server block. The defaults.conf file should be included on the majority of sites, which contains sensible defaults for caching, file exclusions and security. Additional .conf files can be included as needed on a per-site basis.

sites-available - configurations for individual sites (virtual hosts).

sites-enabled - symlinks to configurations within the sites-available directory. Only sites which have been symlinked are loaded.

The following site structure is used throughout this repository:

.
├── yourdomain1.com
    └── cache
    └── logs
    └── public
├── yourdomain2.com
    └── cache
    └── logs
    └── public