How To Install LEMP stack (Linux, Nginx, MySQL, PHP) on Ubuntu System

Harish Kumar · · 4034 Views
How To Install LEMP stack (Linux, Nginx, MySQL, PHP) on Ubuntu System

The term LEMP is an acronym of the four open-source projects:

  1. L - Linux operating system

  2. E - Nginx [engine x]

  3. M - MySQL or MariaDB 

  4. P - PHP programming language

In this post, you will learn how to install Nginx, create Nginx server blocks (virtual host), install and secure MySQL, and install PHP.

Prerequisites

The first thing you should make sure you have a regular, non-root user account on your server with sudo privileges

Step 1. Installing Nginx

Nginx is available in Ubuntu repositories. So, update the packages index and install Nginx by using the following commands on the terminal:

sudo apt update
sudo apt install nginx

Step 2. Installing MySQL

Now the web server is ready. The next step is to install MySQL (a database management system). Install MySQL by using following command:

sudo apt install mysql-server

When the installation is finished, run the mysql_secure_installation command to improve the security of the MySQL installation:

sudo mysql_secure_installation

It will ask to set the root secret password, delete the anonymous user, and remove the test database. You should answer "Y" (yes) to all questions.

Step 3. Installing PHP

Since Nginx doesn't contain native PHP handling like some other web servers, you will need to install php-fpm, which stands "fastCGI process manager”. We will tell Nginx to pass PHP requests to this software for processing.

Install the php-fpm module along with an additional helper package using following commands:

sudo apt install php-fpm php-opcache php-cli php-gd php-curl php-mysql

Step 4: Configuring Nginx to Use the PHP Processor (create virtual hosts)

Now all of the necessary LEMP stack parts installed. Yet still, need to make a couple of configuration changes so as to tell Nginx to utilize the PHP processor for dynamic content.

This is done on the server block level (server blocks are like Apache's virtual hosts). To do this, navigate to /etc/nginx/sites-available/ directory.

Let's say our domain name is example.com. So, here I will create the new server block configuration file is named example.com, although you can name it whatever you’d like:

sudo vi /etc/nginx/sites-available/example.com

Add the following snippet, which was taken and somewhat modified from the default server block configuration file to the new server block configuration file:

In the /etc/nginx/sites-available/example.com  :

server {
        listen 80;
        root /var/www/html;
        index index.php index.html index.htm index.nginx-debian.html;
        server_name example.com;

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

        location ~ \.php$ {
                include snippets/fastcgi-php.conf;
                fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
        }

        location ~ /\.ht {
                deny all;
        }
}

This is what every one of these directives and location blocks does:

  1. listen - Defines what port Nginx should listen on. In this case, that is port 80, which is the default port for HTTP.

  2. root -  Defines the website root path.

  3. index -  prioritize serving files named index.php

  4. server_name - server’s domain name or public IP address.

  5. location / - It has a try_files directive, which checks for the existence of files matching a URI request. If Nginx cannot find it, then it will return a 404 error.

  6. location ~ \.php$ - In this location block, it is pointing Nginx to the fastcgi-php.conf configuration file and the php7.4-fpm.sock file to handle PHP processing.

  7. location ~ /\.ht - This location block tells the Nginx to do not server .htaccess files by using the deny all directive.

After adding this snippet, save and close the file.

The next step is to create a symbolic link from /etc/nginx/sites-available/example.com to the /etc/nginx/sites-enabled/example.com to enable this server block.

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

Test your new configuration file for syntax errors by following command:

sudo nginx -t

If any errors are reported, go back and recheck your configuration file before continuing.

When you are ready, reload Nginx for the changes to take effect:

sudo systemctl reload nginx

This concludes the installation and configuration of your LEMP stack.

1

Please login or create new account to add your comment.

1 comment
gurpreet
gurpreet ·

Good explaination

You may also like:

PHP Security Guide: Strategies for Safe and Secure Code

PHP is one of the most widely used server-side scripting languages for web development, powering millions of websites and applications. Its popularity is largely due to its ease (...)
Harish Kumar

How to Use DTOs for Cleaner Code in Laravel, Best Practices and Implementation Guide

When developing APIs in Laravel, ensuring your responses are clear, concise, and consistent is crucial for creating a maintainable and scalable application. One effective way to (...)
Harish Kumar

Data Transfer Objects (DTOs) in PHP: Streamlining Data Flow and Enhancing Code Clarity

Data Transfer Objects (DTOs) are simple objects used to transfer data between software application subsystems. They help in encapsulating data and reducing the number of method (...)
Harish Kumar

PHP Generators: Efficient Data Handling and Iteration Techniques

PHP Generators offer a powerful and memory-efficient way to handle large datasets and complex iteration scenarios in your applications. They provide a more elegant solution compared (...)
Harish Kumar

Compress and Download Files in Laravel Using ZipArchive with Examples

In web development, file compression is essential for optimizing data transfer and storage. Laravel provides tools for creating and downloading compressed files. This guide explores (...)
Harish Kumar

Understanding Linux File Permissions and Ownership

Linux file permissions are a critical cornerstone in the architecture of Linux systems, serving as a fundamental aspect of their security model. They meticulously define who can (...)
Harish Kumar