Birmingham mumbai

[
 366 
]
Before we do so, I want to mention first that you can really only have one web 
server service running on a single web server. If you've been following along up to 
now, you currently have a functional Apache web server. If you were to also install 
NGINX, it probably wouldn't start as the ports it wants to listen on (port 
80
 and/or 
443
) will already be in use. You can run both on a single server, but that's outside the 
scope of this book. Ideally, you'd want to use one or the other. Therefore, to continue 
with this section you'd either want to remove Apache or set up a separate web 
server for testing NGINX. I recommend the latter, because later on in this chapter we 
will take a look at hosting Nextcloud and we will be using Apache to do so. If you 
remove Apache now, you'd have to add it back in order to follow along with that 
section. Theoretically, you'd only have to stop the 
apache2
 process before starting 
nginx
, but the two resources sharing the same server has a lot of variables and may 
conflict.
To get started with NGINX, simply install it:
sudo apt install nginx
Just like with Apache, if we enter the IP address of our server in a browser, we're 
presented with a sample page, but this time NGINX's version instead of the one that 
ships with Apache. It certainly looks boring in comparison, but it works:
Figure 14.3: The NGINX sample page
The default configuration files for 
nginx
 are stored in the 
/etc/nginx
 directory. 
Go ahead and peruse these files to get a general feel for how the configuration is 
presented. Similar to Apache, you also have a 
sites-enabled
 and 
sites-available
 
directory here, which serve the same purpose.

---

Chapter 14