{"id":81,"date":"2016-09-17T15:59:13","date_gmt":"2016-09-17T15:59:13","guid":{"rendered":"https:\/\/draculaservers.com\/tutorials\/?p=81"},"modified":"2024-01-18T13:57:47","modified_gmt":"2024-01-18T13:57:47","slug":"install-wordpress-lemp-stack-ubuntu-14-04-server","status":"publish","type":"post","link":"https:\/\/draculaservers.com\/tutorials\/install-wordpress-lemp-stack-ubuntu-14-04-server\/","title":{"rendered":"How to Install WordPress with LEMP Stack on an Ubuntu 14.04 Server"},"content":{"rendered":"

A bit about WordPress<\/h2>\n

Most’ve heard about WordPress by now, being one of the most used CMS(content management system) out there. It permits users of all levels of experience to easily create and manage blogs and sites.<\/p>\n

In the following there will be a step by step guide on installing WordPress on a Ubuntu 14.04 server, using Nginx as a web server.<\/p>\n

What you’ll need<\/h2>\n

Installing and configuring a LEMP (Linux operating system, Nginx, MySQL, and PHP) stack on your server. For the installation and setting up process, see the tutorial on installing a LEMP stack on Ubuntu 14.04<\/a>.<\/p>\n\n

Step 1 \u2014 Creating a MySQL Database and User for WordPress<\/h2>\n

After having installed the LEMP stack, we now have MySQL, but no database created for WordPress. So we’ll need to create one, along with a user account that will allow WordPress to access said database.<\/p>\n

Begin by logging in with the following:<\/p>\n

mysql \u2013u root \u2013p\r\n<\/pre>\n
Then you will be required to introduce the password you used for the root account when you installed MySQL , and afterwards a MySQL command prompt will be given.<\/p>\n
Ok, now we’ll be moving on to creating a database that wil be used only by your WordPress application. Baptize your database wisely for easier recognition, in our case we called it wordpress.<\/p>\n
CREATE DATABASE wordpress;\r\n<\/pre>\n
A reminder for first time MySQL users, always make sure each statement ends with a semicolon ( ;).<\/p>\n
Now we shall create that user account we’ve been talking about. This new user will have control of the database we created so that our application can interact with it. Creating a separate user and database for each app is an effective way for managing and keeping data secure in MySQL.<\/p>\n
CREATE USER wordpressuser@localhost IDENTIFIED BY \u2018password';\r\n<\/pre>\n
Now we need to make a connection between the user and database so that MySQL knows this new user can control the database:<\/p>\n
GRANT ALL PRIVILEGES ON wordpress.* TO wordpressuser@localhost;\r\n<\/pre>\n
Ok, now, for our current instance of MySQL to be up to date with the privilege change, we’ll need to flush the former ones:<\/p>\n
FLUSH PRIVILEGES;\r\n<\/pre>\n
Now exit:<\/p>\n
exit\r\n<\/pre>\n
Step 2 \u2014 Downloading WordPress to your Server<\/h2>\n
We need to download onto our server the WordPress content from the WordPress website. The URL is always the same for the latest stable version of WordPress. Download the file to our user’s home directory:<\/p>\n
cd ~\r\nwget http:\/\/wordpress.org\/latest.tar.gz\r\n<\/pre>\n
The files have been downloaded in a compressed form stored in latest.tar.gz and we can extract the content with the following command which will create a directory named wordpress containing the files:<\/p>\n
tar xzvf latest.tar.gz\r\n<\/pre>\n
To download additional components that we’ll be needing in WordPress, in this case packages that allow the user to work with images and install\/update and manage plugins using SSH, we shall be using apt to get them from Ubuntu’s<\/p>\n
repositories:<\/p>\n
sudo apt-get update\r\nsudo apt-get install php5-gd libssh2-php\r\n<\/pre>\n
Step 3 \u2014 Configuring WordPress<\/h2>\n
Next we need to configure our WordPress instance by modifying the main configuration file in the directory we just made. First you need to get into said directory:<\/p>\n
cd  ~\/wordpress\r\n<\/pre>\n
Here we have a file called wp-config-sample.php that we can copy to use as a base for our confing file:<\/p>\n
cp wp- config\u2013sample.php  wp-config .php\r\n<\/pre>\n
Open the file so that we can make the necessary changes:<\/p>\n
nano wp-config.php\r\n<\/pre>\n
Now we need to insert the information needed for us to connect to the database. First we need to set the DB_NAME,\u00a0DB_USER, and\u00a0DB_PASSWORD parameters, which you’ll find in this file and then we’ll set them to use the database and user
\ndetails created so far:<\/p>\n
\/\/ ** MySQL settings - You can get this info from your web host ** \/\/\r\n\r\ndefine('DB_NAME', 'wordpress'); \/** The name of the database for WordPress *\/\r\ndefine('DB_USER', 'wordpressuser'); \/** MySQL database username *\/\r\ndefine('DB_PASSWORD', 'password'); \/** MySQL database password *\/\r\n<\/pre>\n
After that, save and close the file.<\/p>\n
Step 4 \u2014 Copying the Files to the Document Root<\/h2>\n
Now we need to copy our newly modified config files over to our document root so our server can find and do its thing.<\/p>\n
For the transfer process we’ll be using rsync (which preserves permissions, ownership and data integrity) and we’ll need the location of the default document root of Nginx on Ubuntu 14.04 which is \/usr\/share\/nginx\/html.<\/p>\n
We’ll set up our document root in \/var\/www\/html\/ to prevent us from modifying a directory location controlled by he nginx package (we’ll get to changing our nginx configuration later on).<\/p>\n
Creating a new document root directory:<\/p>\n
sudo mkdir  -p \/var\/www\/html\r\n<\/pre>\n
Copy the files in the new document:<\/p>\n
sudo rsync \u2013avP ~\/wordpress\/  \/var\/www\/html\/\r\n<\/pre>\n
This will ensure that our content from ~\/wordpress directory has been copied into our document root.<\/p>\n
Now into the document root we go so we can make some adjustments:<\/p>\n
cd \/var\/www\/html\/\r\n<\/pre>\n
The current directory structure allows user and group ownership of all our files to our regular user, but our web server only needs to be able to modify only some directories and files. So what now? We can give to the group that our web server runs under group ownership of the files permission so we can open them only when needed.<\/p>\n
Nginx operates under the group called www-data. Enter your account name in the user portion( we’ll be using an account called bill:<\/p>\n
sudo chown -R bill:www-data \/var\/www\/html\/*\r\n<\/pre>\n
Now we’re going to create a new directory for user uploads:<\/p>\n
mkdir wp-content\/uploads\r\n<\/pre>\n
Next we need to assign the new directory the www-data group ownership :<\/p>\n
sudo chown \u2013R :www-data \/var\/www\/html\/wp-content\/uploads\r\n<\/pre>\n
Step 5 \u2014 Modifying Nginx Server Blocks<\/h2>\n
We need to change our nginx configuration to serve content appropriately. By using the default server block as a model for our new server block, we copy it over like so:<\/p>\n
sudo cp \/etc\/nginx\/sites-available\/default  \/etc\/nginx\/sites- available\/wordpress\r\n<\/pre>\n
Open the new file for some changes:<\/p>\n
sudo nano \/etc\/nginx\/sites-available\/wordpress\r\n<\/pre>\n
Now for some more changes:<\/p>\n
server {\r\n        listen 80 default_server;\r\n        listen [::]:80 default_server ipv6only=on;\r\n\r\n        root \/var\/www\/html;\r\n        index index.php index.html index.htm;\r\n\r\n        server_name your_domain.com;\r\n\r\n        location \/ {\r\n                # try_files $uri $uri\/ =404;\r\n                try_files $uri $uri\/ \/index.php?q=$uri&$args;\r\n        }\r\n\r\n        error_page 404 \/404.html;\r\n\r\n        error_page 500 502 503 504 \/50x.html;\r\n        location = \/50x.html {\r\n                root \/usr\/share\/nginx\/html;\r\n        }\r\n\r\n        location ~ \\.php$ {\r\n                try_files $uri =404;\r\n                fastcgi_split_path_info ^(.+\\.php)(\/.+)$;\r\n                fastcgi_pass unix:\/var\/run\/php5-fpm.sock;\r\n                fastcgi_index index.php;\r\n                include fastcgi_params;\r\n        }\r\n}\r\n<\/pre>\n
What we’ve done here is ( some of these changes might be set from your LEMP installation) :<\/p>\n