.

Installer NGINX (bedre end Apache eller Lighttpd) - VPS Bibelen PT 11

English Engelsk (ændring)
  • Digg
  • Twitter
  • Technorati
  • del.icio.us
  • Facebook
  • MySpace
  • Reddit
  • StumbleUpon
  • LinkedIn
  • email

Set Up Unmanaged VPS (4 Newbies) - Del 11: Nginx (bedre end Apache) Web Server

Installer Nginx - Nginx logo

Installation & konfiguration Nginx webserver, tweaking standard fil struktur, derefter oprette en vhost-fil med symbolsk er genstand for denne copy / paste how-to. Så åbne, at CLI og jeg vil forklare.

Så vi er klar til at installere en stjerne attraktion, Nginx (udtales "motor-x"). Men hvorfor? Er ikke Apache det bedste web-serveren?

Apache har tjent mig godt i år, både lokalt og på eksterne værter, og er stadig en ønskelig valg for mange store websteder.

Men, lidt ligesom Ubuntu, FireFox og jQuery, er der en ny dreng i byen, og det er slankere, enklere at konfigurere og bruge, og hurtigere at tjene. Indtast Nginx webserveren.

Konfigurer en unmanaged VPS (4 Newbies) .. VPS Bibelen

I 20 kopier / indsæt skridt .. fra nul til helten, tomt felt til cute-som Linux-server.

Rul ned for hele serien indekset.

Så hey, kaste delt & viva virtuelle! Håber det hjælper. The_guv

Video: Install & Configure Nginx Web Server

Se den, er, guvideo for en bedre idé om, hvordan du gør dette.

Check out the_guv's YouTube kanal på http://youtube.com/guvnrDOTcom

... eller hvis du ikke gider med det, eller selv om du kan, her er den detalje ...

Hvorfor vælge Nginx? Hvorfor ikke Apache eller Lighttpd?

Jeg kan ikke bekende sig til at være ekspert, bare en, der har forsket i ultra-grundigt. Jeg primært koncentreret sig om de to mest populære, mest veletablerede webservere, Apache og Lighttpd, og den unge Turk alternativ, Nginx, om hvilken geekdom er alle aflutter. Her er et sammendrag af mine vigtigste resultater: --

  • Apache er bloatware, lastning ubrugte moduler, at spilde ressourcer
  • Lighttpd utætheder RAM dårligt
  • Nginx benchmarks den hurtigste, ved hjælp af mindst ressourcer

Jeg har brugt denne letvægts-server til min ressource-tunge WordPress blog, guvnr.com, og jeg er imponeret over sin solide præstationer. Også vigtigt, har det ikke, at Windows-lignende tendens, en Apache Trængselen for, for at spilde ressourcer ved at køre et bundt af tjenester, som jeg bare ikke har brug for.

Du må ikke tage mit ord for det. Du bør ikke, fordi jeg ikke har foretaget nogen benchmark test. Google noget som Apache vs Nginx "eller Nginx vs Lighttpd og har læst. Og her er Nginx wiki.

Kom i den nyeste Nginx Version

Der er to måder at installere software på Linux, at bruge den integrerede anlæg, redskaber eller fra kildekode.

Normalt, vi installerer internt ved hjælp af noget som den Linux-installer 'aptitude', men fordi det er sådan en vigtig del af vores VPS, jeg skal vise dig, hvordan du installerer fra kilden. Denne metode tager lidt længere tid, men det er det værd, fordi vi vil have en langt mere up-to-date version.

.. Med en web-server, skal vi ikke skære hjørner. Det ville være som at købe en gul Ferrari.

Først op, vi har brug for en vis afhængighed filer: --

sudo aptitude -y install libpcre3 libpcre3-dev libpcrecpp0 libssl-dev zlib1g-dev

And to create a directory in which to store the Nginx package:-

mkdir ~/sources

Change to that directory:-

cd ~/sources/

Now we get the latest stable Nginx release, nginx-0.7.62 *.

* As of September 2009, edited by the_guv. You should still check it is still the latest, here , and ammend the filename accordingly:-

wget http://sysoev.ru/nginx/nginx-0.7.62.tar.gz

Unzip it:-

tar -zxvf nginx-0.7.62.tar.gz

Go into the new unzipped folder:-

cd nginx-0.7.62

Installing and Testing Nginx

Compile with two options; where to install it, and including 'ssl' (to enable 'https' for secure connections, ie shopping and stuff):-

./configure --sbin-path=/usr/local/sbin --with-http_ssl_module

Install this baby:-

make
sudo make install

Kick it up:-

sudo /usr/local/sbin/nginx

And test it by popping your IP address in a web browser. You should see "Welcome to nginx!"

Now stop it:-

sudo kill `cat /usr/local/nginx/logs/nginx.pid`

Have Nginx Start, Restart or Stop When Required

This is important, for example, upon reboot. We need a script for this. Create a file:-

sudo nano /etc/init.d/nginx

And paste this within:-

#! /bin/sh

### BEGIN INIT INFO
# Provides:          nginx
# Required-Start:    $all
# Required-Stop:     $all
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: starts the nginx web server
# Description:       starts nginx using start-stop-daemon
### END INIT INFO

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/local/sbin/nginx
NAME=nginx
DESC=nginx

test -x $DAEMON || exit 0

# Include nginx defaults if available
if [ -f /etc/default/nginx ] ; then
        . /etc/default/nginx
fi

set -e

case "$1" in
  start)
        echo -n "Starting $DESC: "
        start-stop-daemon --start --quiet --pidfile /usr/local/nginx/logs/$NAME.pid \
                --exec $DAEMON -- $DAEMON_OPTS
        echo "$NAME."
        ;;
  stop)
        echo -n "Stopping $DESC: "
        start-stop-daemon --stop --quiet --pidfile /usr/local/nginx/logs/$NAME.pid \
                --exec $DAEMON
        echo "$NAME."
        ;;

  restart|force-reload)
        echo -n "Restarting $DESC: "
        start-stop-daemon --stop --quiet --pidfile \
                /usr/local/nginx/logs/$NAME.pid --exec $DAEMON
        sleep 1
        start-stop-daemon --start --quiet --pidfile \
                /usr/local/nginx/logs/$NAME.pid --exec $DAEMON -- $DAEMON_OPTS
        echo "$NAME."
        ;;
  reload)
      echo -n "Reloading $DESC configuration: "
      start-stop-daemon --stop --signal HUP --quiet --pidfile /usr/local/nginx/logs/$NAME.pid \
          --exec $DAEMON
      echo "$NAME."
      ;;
  *)
        N=/etc/init.d/$NAME
        echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
        exit 1
        ;;
esac

exit 0

Then give the file permissions and make the script run on reboot, else start/stop/restart when required:-

sudo chmod +x /etc/init.d/nginx
sudo /usr/sbin/update-rc.d -f nginx defaults

nginx.conf - Configuring Nginx

Now open the Nginx configuration file:-

sudo nano /usr/local/nginx/conf/nginx.conf

...and strip out all the content, delete the lot. CTRL-K is the easy way to do that, if you were wondering.

And replace with this:-

user www-data www-data;
worker_processes  4;

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

    sendfile        on;
    tcp_nopush      on;
    tcp_nodelay     off;
    keepalive_timeout  5;

    gzip  on;
    gzip_comp_level 2;
    gzip_proxied any;
    gzip_types      text/plain text/css application/x-javascript text/xml application/xml application/xml+rss text/javascript;

    include /usr/local/nginx/sites-enabled/*;
}

Creating the Virtual Host File Structure & Symlinks

The Nginx file structure is pretty messy for multiple sites, so we'll sort that.

First, layout some new folders:-

sudo mkdir /usr/local/nginx/sites-available
sudo mkdir /usr/local/nginx/sites-enabled

...the first is for our virtual host (vhost) files, the second for their corresponding symlinks which will be referenced by Nginx' config file.

What are vhosts & symlinks?

You have one of each per domain, and one of each for the default settings.

The symlink, or symbolic link, references the web server to the virtual host file.

The vhost file is a configuration file. It tells the web server, for example, things like where the web files live or the kind of URI structure you want.

For now, we need a default vhost file, and that goes in the sites-available folder. So:-

sudo nano /usr/local/nginx/sites-available/default

Now paste this:-

server  {
            listen       80;
            server_name  localhost;
            
            location /  {
                    root   html;
                    index  index.php index.html index.htm;
       			   }
                       
            # redirect server error pages to the static page /50x.html
            error_page   500 502 503 504  /50x.html;
            location = /50x.html 
            		   {
            			root   html;
            		   }
		}

And enable it with this symlink:-

sudo ln -s /usr/local/nginx/sites-available/default /usr/local/nginx/sites-enabled/default

Boot it up again:-

sudo /etc/init.d/nginx start

...and check for that "Welcome..." page again, using your IP in a web browser.

Splendid. All pretty. And pretty well organised.

Moving Along

So that's Nginx up and running.

In Part 12 of this series Set Up an Unmanaged VPS (4 Newbies) I'm taking a quick detour, setting up FileZilla so we've got a Secure FTP (SFTP) connection. That'll be handy to help demonstrate Part 13, when we create another folder structure, this time for our sites and blogs, and pop up a couple of test pages.

Then, in Part 13, I'll show you how to use Subversion to more easily install and upgrade platforms and their modules/plugins. I'll example the popular WordPress scenario - and while we're about it we'll sort out WordPress caching and friendly-URLs.

And then, this, that, the other. Cue index ..


SETUP an Unmanaged VPS (4 Newbies) .. The V-P-S Bible

Serve multi sites & blogs on a budget .. at the fastest possible speed .. with the least downtime .. in the most secure environment .. and future-proofed for easy admin.

That's what the VPS Bible is about, stepped out in simple copy & paste guides.

From high traffic WordPress blogs to startup web hosts, here's what you need.

Set it up?   Click here for the 21 part follow-up .. V-P-S Admin

  1. * Includes video tutorial.

  2. Not linked = not published. Won't be long. Fix a feed for updates.


If you liked that ...

.