首先要开启模块mod_proxy, httpd.conf:

很久之前的笔记了，现在整理出来, 这里采用的是Apache + Mongrel Cluster, 其实shitou个人还是喜欢Lighttpd + FastCGI搭配的说，因为其他原因只能现在跑这样的环境啦- -||

软件:

ruby-1.8.7-p72.tar.gz

rubygems-1.3.0.tgz

ruby-zlib-0.6.0.tar.gz

mysql-ruby-2.8.tar.gz

安装:

安装ruby

#apt-get install gcc libc6-dev make tmake autogen automake \

build-essential indent intltool

#tar zxvf ruby-1.8.7-p72.tar.gz

#cd ruby-1.8.7-p72

##开启最后一行的zlib支持

#vi ext/Setup

#./configure --prefix=/usr/local/ruby

#make; make install

##把/usr/local/ruby/bin加入环境变量PATH中, 并写入文件/root/.profile中

#apt-get install zlib1g-dev

#cd ext/zlib

#ruby extconf.rb;

#make; make install

安装rubygems

#tar zxvf rubygems-1.3.0.tgz

#cd rubygems-1.3.0

#ruby setup.rb

安装rails

#gem install rails –version 2.0.2

支持rails console

#apt-get install libreadline5-dev

#cd ruby-1.8.7-p72/ext/readline

#ruby extconf.rb

#make; make install

在不安装SSL的话rails应用启动会报错

#apt-get install libssl-dev

#cd ruby-1.8.7-p72/ext/openssl

#ruby extconf.rb

#make; make install

安装mysql

#apt-get install mysql-server mysql-client libmysqlclient15-dev

安装ruby的mysql的C接口

#tar zxvf mysql-ruby-2.8.tar.gz

#cd mysql-ruby-2.8

#ruby extconf.rb –with-mysql-include=/usr/include/mysql –with-mysql-lib=/usr/lib

#make; make install

安装mongrel

#gem install mongrel mongrel_cluster

Apache, PHP的安装

#apt-get install apache2

#apt-get install php5 php5-mysql libapache2-mod-php5 php-pear

mongrel的配置

/railsapp/config/mongrel_cluster.yml:

cwd: /var/www/rails/cal_point
port: 3000
environment: production
group: www-data
user: www-data
address: 127.0.0.1
pid_file: log/mongrel.pid
servers: 3

Apache开启Proxy的相关模块, 配置

/etc/apache2/httpd.conf:

<Proxy balancer://myproxycluster>
    #loadfactor is the weight of the server, range 1-100, the bigger the stronger
    BalancerMember http://127.0.0.1:3000    loadfactor=10
    BalancerMember http://127.0.0.1:3001    loadfactor=10
    BalancerMember http://127.0.0.1:3002    loadfactor=10
</Proxy>

ProxyPass / balancer://myproxycluster/
ProxyPassReverse / balancer://myproxycluster/

启动mongrel cluster:

进去rails项目的根目录:

#mongrel_rails cluster::start

注意: 启动前要保正log文件夹的权限为Apache运行用户(在debian中一般是www-data)可写的

在Lighttpd的wiki上看大一篇很好的文档，里面也有troubleshooting, 转过来了，本来是想找Lighttpd防webspider的资料的，
根据下面的说明使用$HTTP["useragent"]这个变量可以达到效果


#!rst
==================
Configuration File
==================

------------
Module: core
------------

.. meta::
  :keywords: lighttpd, configuration

.. contents:: Table of Contents

Description
===========

Basic Syntax
------------

A BNF like notation: ::

  option   : NAME = VALUE
  merge    : NAME += VALUE
  NAME     : modulename.key
  VALUE    : (  |  |  |  | VALUE [ + VALUE ]*)
   : "text" 
  : digit*
  : ( "enable" | "disable" )
    : "(" [  "=>" ]  [, [  "=>" ]  ]* ")" 
  INCLUDE  : "include" VALUE
  INCLUDE_SHELL : "include_shell" STRING_VALUE

Example
-------

::

  # default document-root
  server.document-root = "/var/www/example.org/pages/" 

  # TCP port
  server.port = 80

  # selecting modules
  server.modules = ( "mod_access", "mod_rewrite" )

  # variables, computed when config is read.
  var.mymodule = "foo" 
  server.modules += ( "mod_" + var.mymodule )
  # var.PID is initialised to the pid of lighttpd before config is parsed

  # include, relative to dirname of main config file
  include "mime.types.conf" 

  # read configuration from output of a command
  include_shell "/usr/local/bin/confmimetype /etc/mime.types" 

Conditional Configuration
=========================

Most options can be configured conditionally by using the following syntax
(including nesting).

::

     {
    ...
       {
      ... nesting: match only when parent match
    }
  }
  else    {
    ... the "else if" block
  }

where  is one of one of the following:

$HTTP["cookie"]
  match on cookie
$HTTP["host"]
  match on host
$HTTP["useragent"]
  match on useragent
$HTTP["referer"]
  match on referer
$HTTP["url"]
  match on url. If there are nested blocks, this must be the most inner block.
$HTTP["querystring"]
  match on querystring, eg, after the ? in this type url: index.php?module=images..
$HTTP["remoteip"]
  match on the remote IP or a remote Network (Warning: doesn't work with IPv6 enabled)
$HTTP["scheme"] (Introduced in version 1.4.19)
  match on the scheme used by the incoming connection.  This is either "http" or "https".
$SERVER["socket"]
  match on socket. Value must be on the format "ip:port" where ip is an IP address and 
  port a port number, or ":port" to match port only. Only equal match (==) is supported.
  It also binds the daemon to this socket. Use this if you want to do IP/port-based virtual hosts.
$PHYSICAL["path"] (Introduced in version 1.5.0)
  match on the mapped physical path of the file / cgi script to be served.
$PHYSICAL["existing-path"] (Introduced in version 1.5.0)
  match on the mapped physical path of the file / cgi script to be served
  only if such a file exists on the local filesystem.

 is one of:

==
  string equal match
!=
  string not equal match
=~
  perl style regular expression match
!~
  perl style regular expression not match

and  is either a quoted ("") literal string or regular expression.

Example
-------

::

  # disable directory-listings for /download/*
  dir-listing.activate = "enable" 
  $HTTP["url"] =~ "^/download/" {
    dir-listing.activate = "disable" 
  }

  # handle virtual hosting
  # map all domains of a top-level-domain to a single document-root
  $HTTP["host"] =~ "(^|\.)example\.org$" {
    server.document-root = "/var/www/htdocs/example.org/pages/" 
  }

  # multiple sockets
  $SERVER["socket"] == "127.0.0.1:81" {
    server.document-root = "..." 
  }

  $SERVER["socket"] == "127.0.0.1:443" {
    ssl.pemfile = "/var/www/certs/localhost.pem" 
    ssl.engine = "enable" 

    server.document-root = "/var/www/htdocs/secure.example.org/pages/" 
  }

  # deny access for all googlebot
  $HTTP["useragent"] =~ "Google" {
    url.access-deny = ( "" )
  }

  # deny access for all image stealers (anti-hotlinking for images)
  $HTTP["referer"] !~ "^($|http://www\.example\.org)" {
    url.access-deny = ( ".jpg", ".jpeg", ".png" )
  }

  # deny the access to www.example.org to all user which 
  # are not in the 10.0.0.0/8 network
  $HTTP["host"] == "www.example.org" {
    $HTTP["remoteip"] != "10.0.0.0/8" {
     url.access-deny = ( "" )
    }
  }

  # Allow only 200.19.1.5 and 210.45.2.7 to
  # have access to www.example.org/admin/
  $HTTP["host"] == "www.example.org" {
    #!~ is a perl style regular expression not match
    $HTTP["remoteip"] !~ "^(200\.19\.1\.5|210\.45\.2\.7)$" {
      $HTTP["url"] =~ "^/admin/" {
        url.access-deny = ( "" )
      }
    }
  }

Troubleshooting
---------------

If you're not running on the default port, $HTTP["host"] will have the port appended to it, 
so regular expressions ending in "$" (without allowing for a port) won't match. 
To match with or without a port, change "(^|\\.)example\\.org$" to "(^|\\.)example\\.org(\\:[0-9]*)?$" 

advanced usage
==============
check the blog:
http://blog.lighttpd.net/articles/2005/05/07/advanced-configuration-in-up-upcoming-1-4-x

Using variables
===============

You can set your own variables in the configuration to simplify your config.
::

  var.basedir = "/home/www/servers/" 
  $HTTP["host"] == "www.example.org" {
     server.name = "www.example.org" 
     include "incl-base.conf" 
  }

  in incl-base.conf:
  server.document-root = basedir + server.name + "/pages/" 
  accesslog.filename   = basedir + server.name + "/logs/access.log" 

You can also use environment variables or the default variables var.PID and
var.CWD: ::

  var.basedir = env.LIGHTTPDBASE

  $HTTP["host"] == "www.example.org" {
     server.name = "www.example.org" 
     include "incl-base.conf" 
     include "incl-fastcgi.conf" 
  }

  in incl-fastcgi.conf:
  fastcgi.server = ( ... => ((
     "socket" => basedir + server.name + "/tmp/fastcgi-" + PID + ".sock" 
  )) )

Or like the lighttpd script for rails does: ::

  var.basedir = var.CWD

  server.document-root = basedir + "/public/" 

Some useful things that can NOT be done in lighttpd config (you need to 
create a script in a real programming language and than use include_shell): ::

  # testing if a variable has been set is NOT possible
  var.not_sure_if_it_exists == undefined { ... set to default value ... }

  # removing from arrays is NOT possible
  server.modules -= ( "mod_idontwantyou" )

Global context
==============

::

  global {
    ...
  }

You don't need it in the main configuration file. But you might have
difficulty setting a server wide configuration inside a included-file from
conditionals.

Example
-------

::

  in lighttpd.conf:
  server.modules = ()
  $HTTP["host"] == "www.example.org" {
    include "incl-php.conf" 
  }

  in incl-php.conf:
  global {
    server.modules += ("mod_fastcgi")
    static-file.exclude-extensions += (".php")
  }
  fastcgi.server = "..." 

Options
=======

`All Configuration Options`__

.. __: http://trac.lighttpd.net/trac/wiki/Docs%3AConfigurationOptions

Etag

在HTTP1.1中有介绍，主要的作用就是在(css file, image, javascript file)文件后面添加一个唯一的参数（相当于查询参数字符串），Etag有服务器端生成，并且随着文件的改变而改变，这样浏览器端就会只重新请求获取Etag发生变化的文件，减少浏览器端数据的流量，加快浏览器的反应速度，重要的是减轻服务器端的压力，所以服务器端Etag的实现就比较重要了。

下面分别说下在Apache和Lighttpd中怎样配置Etag

Apache Etag

在Apache中设置Etag的支持比较简单，只用在含有静态文件的目录中建立一个文件.htaccess, 里面加入：

FileETag MTime Size

这样就行了，详细的可以参考Apache的文档页：Documentation

Lighttpd Etag

在Lighttpd中设置Etag支持：

etag.use-inode: 是否使用inode作为Etag

etag.use-mtime: 是否使用文件修改时间作为Etag

etag.use-size: 是否使用文件大小作为Etag

static-file.etags: 是否启用Etag的功能

第四个参数肯定是要enable的， 前面三个就看实际的需要来选吧，推荐使用修改时间

Expires

过期时间是HTTP响应(response)的头部控制信息,浏览器会在指定过期时间内使用本地缓存，不用重新加载，对应的缓存对象主要是静态文件，如css，image， javascript； 可以在服务器端进行全局设置，也可以应用端进行设置，这里我会说下服务器端的设置

Apache

首先要确定Apache是否支持了mod_expired模块

然后在Apache的配置文件中加入：

  
       ExpiresActive on
       ExpiresDefault "access plus 1 year"
   

可以看出，配置时可以指定设置Expire对象的文件类型，以及过期时间，这里是一年后

Lighttpd 

Lighttpd设置expire也要先查看是否支持了mod_expire模块，查看vlighttpd.conf文件中
是否开启了该模块

然后就可以设置了：

下面的设置是让URI中所有images目录下的文件1小时后过期；
expire.url = ( "/images/" => "access 1 hours" )
下面是让作用于images目录及其子目录的文件；
$HTTP["url"] =~ "^/images/" {
     expire.url = ( "" => "access 1 hours" )
}
也可以指定文件的类型；
$HTTP["url"] =~ "\.(jpg|gif|png|css|js)$" {
     expire.url = ( "" => "access 1 hours" )
}

其他

设置较长的过期时间后如果想要客户端重新下载文件怎么办呢，比如当你修改了javascript或者

是css文件后，这时可以改变文件的文件名，最合适的做法是给文件加上一个版本号，

比如main_1.0.1.js, 这也是yahoo的做法。

当服务器的环境是cluster时，Etag的使用可能就要考虑的更多了，因为每个服务器生成的Etag

不一样，所以最终的浏览器每次都检测到文件的Etag不一样而去重新请求，这里就不多说了，
注意到这个问题就行了，好了，说完了

原文链接：原文

由于rails的逐渐流行,各种的web服务器也逐渐开始流行起来,搜集点nginx的资料:

nginx的wiki: http://wiki.codemongers.com/NginxChs

Nginx ("engine x") 是一个高性能的 HTTP 和 反向代理 服务器，也是一个 IMAP/POP3/SMTP 代理服务器。 Nginx 是由 Igor Sysoev 为俄罗斯访问量第二的 Rambler.ru 站点开发的，它已经在该站点运行超过两年半了。Igor 将源代码以类BSD许可证的形式发布。尽管还是测试版，但是，Nginx 已经因为它的稳定性、丰富的功能集、示例配置文件和低系统资源的消耗而闻名了。

因 为 Nginx 的文档大部分是俄文的，本维基的目的是帮助使用中文世界的用户安装、配置和交换有关 Nginx 的使用经验。大部分文档源自Aleksandar Lazic 的工作。有关本维基本身的问题请直接询问Cliff Wells 。

其他翻译请点击


官方说明: http://nginx.net/

Basic HTTP features:

• Handling of static files, index files, and autoindexing; open file descriptor cache;
• Accelerated reverse proxying without caching; simple load balancing and fault tolerance;
• Accelerated support without caching of remote FastCGI servers; simple load balancing and fault tolerance;
• Modular architecture. Filters include gzipping, byte ranges, chunked responses, and SSI. Multiple SSI inclusions within a single page can be processed in parallel if they are handled by FastCGI or proxied servers.
• SSL and TLS SNI support.

Mail proxy server features:

• User redirection to IMAP/POP3 backend using an external HTTP authentication server;
• User authentication using an external HTTP authentication server and connection redirection to internal SMTP backend;
• Authentication methods:
  • POP3: USER/PASS, APOP, AUTH LOGIN PLAIN CRAM-MD5;
  • IMAP: LOGIN, AUTH LOGIN PLAIN CRAM-MD5;
  • SMTP: AUTH LOGIN PLAIN CRAM-MD5;
• SSL support;
• STARTTLS and STLS support.

Tested OS and platforms:

• FreeBSD 3 — 7 i386; FreeBSD 5 — 7 amd64;
• Linux 2.2 — 2.6 i386; Linux 2.6 amd64;
• Solaris 9 i386, sun4u; Solaris 10 i386, amd64, sun4v;
• MacOS X ppc, i386;

Architecture and scalability:

• one master process and several workers processes. The workers run as unprivileged user;
• kqueue (FreeBSD 4.1+), epoll (Linux 2.6+), rt signals (Linux 2.2.19+), /dev/poll (Solaris 7 11/99+), event ports (Solaris 10), select, and poll support;
• various kqueue features support including EV_CLEAR, EV_DISABLE (to disable event temporalily), NOTE_LOWAT, EV_EOF, number of available data, error codes;
• sendfile (FreeBSD 3.1+), sendfile (Linux 2.2+), sendfile64 (Linux 2.4.21+), and sendfilev (Solaris 8 7/01+) support;
• accept-filter (FreeBSD 4.1+) and TCP_DEFER_ACCEPT (Linux 2.4+) support;
• 10,000 inactive HTTP keep-alive connections take about 2.5M memory;
• data copy operations are kept to a minimum.

Other HTTP features:

• name- and IP-based virtual servers;
• keep-alive and pipelined connections support;
• flexible configuration;
• reconfiguration and online upgrade without interruption of the client processing;
• access log formats, bufferred writing, and quick log rotation;
• 4xx-5xx error codes redirection;
• rewrite module;
• access control based on client IP address and HTTP Basic authentication;
• PUT, DELETE, MKCOL, COPY and MOVE methods;
• FLV streaming;
• speed limitation;
• limitation of simultaneous connections from one address.

从网上的信息看nginx的性能还是非常强大,官方介绍里的特性有很多也是非常吸引人的,
rewrite, proxy的特性就不说了,还支持FLV streaming,做视频网站非常不错,可以结合Lighttpd.
其他的负载均衡能力好象也很强悍,据说超过了Pound,Apache mod_proxy_balancer.
另外静态文件的传输能力也超过了Lighttpd.不过好象国内使用的人还不是很多,在CU上搜了下没什么相关帖子
等有时间了做下实验,看看咋样~

这有几篇不错的文档,先把地址放这,做实验时用:)

https://calomel.org/nginx.html
http://en.wikipedia.org/wiki/Nginx

http://docs.planetargon.com/Nginx_Configuration/

http://blog.kovyrin.net/2006/04/17/typical-nginx-configurations/