Install wordpress in nginx debian included the following
Budget: $10 – $30 USD
Use Nginx as the web server. Use the latest version of Nginx available.
● Nginx should be in front. It should be publicly exposed. It should also be used to serve
all static content for Wordpress, which includes JS, CSS and image files. For everything
else, it should forward the request to its backend, which should be PHP-FPM.
● Use PHP 7.x (any stable 7 series version). For serving PHP requests, use PHP-FPM. It
should work with the version of PHP you have chosen.
● Use either MySQL or MariaDB for the database. Latest versions of either. The
connection between PHP-FPM and database should be on unix domain sockets, and not
over TCP/IP.
● Apart from SSH access, your server should only have access open to ports 80 and 443.
No other ports should be publicly listening. You can use any approach to achieve this as
you feel comfortable.
In the end, your web request and response cycle should follow this pattern:
The web request comes to Nginx on the front. If it is a request for static assets, Nginx serves it
from its cache. If it is not, then Nginx forwards the request to PHP-FPM which loads the
resulting PHP files/pages. PHP-FPM also connects with the database for any dynamic data it
wants to load from the database.
Getting a domain for your site
In order to fully set up Wordpress you will need a domain name. Try and find one of those free
domain sites that offer not only a free domain/subdomain but also limited DNS managing
features so you can point your free domain to your Cloud server.
Deploying Wordpress
Finally, the Wordpress that you deploy should be deployed via Git. You may host a brand new
copy of Wordpress on either GitHub or BitBucket, and use a “deployment” key to pull the code
on your server.
Automating Wordpress backup on your server
Write a bash script to automate backups for Wordpress. This should backup as much as is
necessary to restore Wordpress in the event of failure. The script should be set up to run once
every day but at a non-peak hour.
Securing your Wordpress
Set up a self-signed SSL certificate on your server for your Wordpress site. Your SSL
connection should be terminated at Nginx. Once you have configured your self-signed SSL
certificate, you have to make sure that your Wordpress website opens only on SSL/HTTPS.
There should also be no mixed-content issues anywhere on the site.
Now, remove or disable the self-signed setup, and install a Let’s Encrypt SSL on your site. The
site should load on SSL by default without any errors or issues
● Nginx should be in front. It should be publicly exposed. It should also be used to serve
all static content for Wordpress, which includes JS, CSS and image files. For everything
else, it should forward the request to its backend, which should be PHP-FPM.
● Use PHP 7.x (any stable 7 series version). For serving PHP requests, use PHP-FPM. It
should work with the version of PHP you have chosen.
● Use either MySQL or MariaDB for the database. Latest versions of either. The
connection between PHP-FPM and database should be on unix domain sockets, and not
over TCP/IP.
● Apart from SSH access, your server should only have access open to ports 80 and 443.
No other ports should be publicly listening. You can use any approach to achieve this as
you feel comfortable.
In the end, your web request and response cycle should follow this pattern:
The web request comes to Nginx on the front. If it is a request for static assets, Nginx serves it
from its cache. If it is not, then Nginx forwards the request to PHP-FPM which loads the
resulting PHP files/pages. PHP-FPM also connects with the database for any dynamic data it
wants to load from the database.
Getting a domain for your site
In order to fully set up Wordpress you will need a domain name. Try and find one of those free
domain sites that offer not only a free domain/subdomain but also limited DNS managing
features so you can point your free domain to your Cloud server.
Deploying Wordpress
Finally, the Wordpress that you deploy should be deployed via Git. You may host a brand new
copy of Wordpress on either GitHub or BitBucket, and use a “deployment” key to pull the code
on your server.
Automating Wordpress backup on your server
Write a bash script to automate backups for Wordpress. This should backup as much as is
necessary to restore Wordpress in the event of failure. The script should be set up to run once
every day but at a non-peak hour.
Securing your Wordpress
Set up a self-signed SSL certificate on your server for your Wordpress site. Your SSL
connection should be terminated at Nginx. Once you have configured your self-signed SSL
certificate, you have to make sure that your Wordpress website opens only on SSL/HTTPS.
There should also be no mixed-content issues anywhere on the site.
Now, remove or disable the self-signed setup, and install a Let’s Encrypt SSL on your site. The
site should load on SSL by default without any errors or issues