Nginx is a popular lightweight server for those who do not need the bulk and extra services that Apache may offer.
This article will look at installing Nginx from source on an Ubuntu Hardy Slice.
At the time of writing, the latest stable version of Nginx is 0.6.31. You can check the latest versions and change logs at the main nginx site.
Do note that Nginx is also available from Hardy's package manager (aptitude) and is at version 0.5.33.
Using the inbuilt package manager will ensure any dependencies are taken care of and any security issue (if any arise) are taken care of with a simple update.
Please see this article if you want to install Nginx with the package manager.
One final difference that is worth considering is the layout differences between using the packaged version and installing from source.
Ubuntu's packaged version of Nginx uses a 'sites-available' and 'sites-enabled' layout in the same manner as a Debian based Apache install.
Although installing from source does not automatically create this layout, I will show how to adjust the folders and config files to do so.
Mirroring the layout used in the packed version of Nginx gives us 'common ground' when moving onto creating virtual hosts and further configuration articles.
As we are not using the package manager to install nginx, we need to take care of some dependencies.
Not many are needed and include pcre, ssl and zlib packages:
sudo aptitude install libpcre3 libpcre3-dev libpcrecpp0 libssl-dev zlib1g-dev
Now we can download the source code.
Create a 'sources' directory (you can download it anywhere you want to):
Now move into the folder:
And then download the source code:
Unpack the downloaded tar file and move into the newly created directory:
tar -zxvf nginx-0.6.31.tar.gz ... cd nginx-0.6.31/
There are quite a few compile time options that are available to use.
Have a look at the Install Options page of the nginx wiki for full details.
We're going to use just two options to customise the install. The first of which is:
By default, nginx will be installed in /usr/local/nginx which, although a good place, does mean the main nginx binary will be found in /usr/local/nginx/sbin/nginx.
Not a location we are likely to find in our default search paths. So instead of adding new directories to our path (which may cause errors later on) we simply define where to put the binary.
The second option is:
Probably self explanatory, but this will enable the ssl module to be compiled so we can parse https requests.
Let's go ahead and compile nginx using those two options:
./configure --sbin-path=/usr/local/sbin --with-http_ssl_module
There will be a nice summary at the end of the compile which includes such items as:
... nginx path prefix: "/usr/local/nginx" nginx binary file: "/usr/local/sbin" nginx configuration file: "/usr/local/nginx/conf/nginx.conf" ...
Keep a note of the output as it does contain some useful paths and locations for various files.
Ok, let's go ahead and 'make' and then 'make install':
make ... sudo make install
Done. We can test the install by starting nginx:
and navigating to our Slice IP address (assuming you have no other server running):
You will be greeted with the standard welcome page:
If you have used Apache or some other web server (or even installing Nginx via a package manager), you may be used to using a script to start and stop it such as you might find in '/etc/init.d/'.
Unfortunately, compiling from source does not create a script like that (we will create an init script in the next article or two).
You may have noticed that one of the paths noted in the compile summary was:
nginx pid file: "/usr/local/nginx/logs/nginx.pid"
Let's make use of that to stop nginx:
sudo kill `cat /usr/local/nginx/logs/nginx.pid`
That will use the output of the pid file to kill the nginx process - note the use of backslashes (`) and not single quotes (') in the command.
Although quite detailed, we have installed the latest version of nginx from source and compiled it with some custom options to make life slightly easier.
We also know how to start and stop nginx by hand.
As mentioned, the next couple of articles will deal with learning how to create an init script so we have more control over Nginx and in mirroring the 'Debian' style layout to include sites-available and sites-enabled folders and so on.
Once done, we will then look at configuring nginx, setting up vhosts and proxying to a backend (such as a cluster of mongrels).