Birmingham mumbai

[
 367 
]
Just as with Apache, the 
sites-available
 directory houses configuration files for 
sites that 
can be
 enabled, while the 
sites-enabled
 directory stores configuration 
files for sites that are enabled. Unlike Apache, though, we don't have dedicated 
commands to enable these sites. We have to link them manually. Although we 
haven't even looked at NGINX configuration files yet, let's just assume that we have 
created the following configuration file:
/etc/nginx/sites-available/acmesales.com
To enable that site, we would need to create a symbolic link for it and store that link 
in the 
/etc/nginx/sites-enabled
 directory:
sudo ln -s /etc/nginx/sites-available/acmesales.com /etc/nginx/sites-
enabled/acmesales.com
Then, we can reload 
nginx
:
sudo systemctl reload nginx
As it stands right now, a site configuration file named 
default
 exists in 
/etc/nginx/
sites-available
 and a symbolic link to it is already present in 
/etc/nginx/sites-
enabled
. If all we want to do is host a single site, we only need to replace the default 
content that NGINX serves, which is located in the 
/var/www/html
 directory (the same 
as Apache) with the content for our site. After refreshing the page, we're good to go.
If we want to serve more than one site from one server, the 
default
 file is a great 
starting point for creating additional virtual hosts. We can start by copying it to a 
new name:
sudo cp /etc/nginx/sites-available/default /etc/nginx/sites-available/
acmesales.com
Now, we can edit this file and change it to serve additional content. First of all, 
only one site can be referred to as a 
default
 site. A default site in NGINX is one that 
answers if none of the other sites match a request. Therefore, we want to remove 
both occurrences of 
default_server
 from our newly copied config. Find these lines:
listen 80 default_server;
listen [::]:80 default_server;
Obviously, 
acmesales.com
 is an example, so feel free to name this 
whatever you wish.

---

Serving Web Content