Nginx+Unicorn+rails多项目

李斯特

使用nginx搭配unicorn来启动多个工程，同时还要照顾过去那些使用lighttpd启动的项目
一、nginx的安装配置
tar zxvf nginx-0.7.67.tar.gz
cd nginx-0.7.67/
./configure
make
make install

默认在/usr/local/nginx/sbin下
执行命令
cd /usr/local/nginx/sbin
./nginx
如是想更换端口 编辑配置文件/usr/local/nginx/conf/nginx.conf 中的配置即可
下面要配置一个工程，通过nginx和unicorn来启动
  创建这个目录待用/tmp/nginx/sockets/
  在nginx配置文件中添加一个
  upstream config_manager {
server unix:/tmp/nginx/sockets/config_manager_unicorn.sock fail_timeout=0;
}

  server中添加
server {
listen       80;
server_name  ***.******.com;
………
……
location ~ ^/config {                 (注：这是一个正则表达式 匹配浏览器地址访地址 的path,这里以config开头的path在这里面处理，也可以直接写成 location /config)
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
proxy_pass http://config_manager;（注：这个config_manager 对应上面的upstream）
}

二、安装unicorn并在项目中添加对应的配置
安装很简单，直接
gem install unicorn

  在工程里面 配置路径下添加(这个是github的配置文件，有很多没用的都贴出来了)
  unicorn.rb
  内容如下：
# unicorn_rails -c /data/github/current/config/unicorn.rb -E production -D
rails_env = ENV['RAILS_ENV'] || 'production'
# 16 workers and 1 master
worker_processes (rails_env == 'production' ? 16 : 4)
# Load rails+github.git into the master before forking workers
# for super-fast worker spawn times
preload_app true
# Restart any workers that haven't responded in 30 seconds
timeout 30
# Listen on a Unix data socket
!!!!!!!!!!!!!!!!!!!!!!!=========下面这个地址要与nginx.conf的upstream相对应
listen '/tmp/nginx/sockets/config_manager_unicorn.sock', :backlog => 2048
##
# REE
# http://www.rubyenterpriseedition.com/faq.html#adapt_apps_for_cow
if GC.respond_to?(:copy_on_write_friendly=)
GC.copy_on_write_friendly = true
end

before_fork do |server, worker|
##
# When sent a USR2, Unicorn will suffix its pidfile with .oldbin and
# immediately start loading up a new version of itself (loaded with a new
# version of our app). When this new Unicorn is completely loaded
# it will begin spawning workers. The first worker spawned will check to
# see if an .oldbin pidfile exists. If so, this means we've just booted up
# a new Unicorn and need to tell the old one that it can now die. To do so
# we send it a QUIT.
#
# Using this method we get 0 downtime deploys.
old_pid = RAILS_ROOT + '/tmp/pids/unicorn.pid.oldbin'
if File.exists?(old_pid) && server.pid != old_pid
begin
Process.kill("QUIT", File.read(old_pid).to_i)
rescue Errno::ENOENT, Errno::ESRCH
# someone else did our job for us
end
end
end
after_fork do |server, worker|
##
# Unicorn master loads the app then forks off workers - because of the way
# Unix forking works, we need to make sure we aren't using any of the parent's
# sockets, e.g. db connection
!!!!!!!!!!!!!!!!!!!=====注释掉了第二行，主要是因为没有开启相应的memcache服务之类======!!!!!!!!!!!!!!!
ActiveRecord::Base.establish_connection
#CHIMNEY.client.connect_to_server
# Redis and Memcached would go here but their connections are established
# on demand, so the master never opens a socket

##
# Unicorn master is started as root, which is fine, but let's
# drop the workers to git:git
begin
uid, gid = Process.euid, Process.egid
user, group = 'root', 'root'
target_uid = Etc.getpwnam(user).uid
target_gid = Etc.getgrnam(group).gid
worker.tmp.chown(target_uid, target_gid)
if uid != target_uid || gid != target_gid
Process.initgroups(user, target_gid)
Process::GID.change_privilege(target_gid)
Process::UID.change_privilege(target_uid)
end
rescue => e
if RAILS_ENV == 'development'
STDERR.puts "couldn't change user, oh well"
else
raise e
end
end
end


配置完成后 访问http://***.***.com/config，会出现config路由不存在，可在工程项目中的config/environment.rb中添加这么一句
ENV['RAILS_RELATIVE_URL_ROOT'] = "/config"

再放个简约的配置
worker_processes 3
listen '/tmp/nginx/sockets/*****.sock', :backlog => 2048
timeout 30
preload_app true
before_fork do |server, worker|
old_pid = pid_file + '.oldbin'
if File.exists?(old_pid) && server.pid != old_pid
begin
Process.kill("QUIT", File.read(old_pid).to_i)
rescue Errno::ENOENT, Errno::ESRCH
# someone else did our job for us
end
end
end

配置完成之后，打开工程目录后，运行：unicorn_rails -c config/unicorn.rb -E production

三、nginx反向代理lighttpd
现在要改用 nginx 做 web server,但是有一些老项目用的 lighttpd。
可以用 nginx 反向代理功能，把一些请求叫给 lighttpd 处理
1 修改 lighttpd 的配置文件
# /etc/lighttpd/lighttpd.conf
# 只允许本机访问  
server.bind = "localhost"  
# 从81端口启动  
server.port                = 81  

2 修改 nginx 的配置文件
# /usr/local/nginx/conf/nginx.conf
http {  
# 新的项目 对应 new.domain.com 域名  
server {  
listen          80;  
server_name     new.domain.com;  
access_log      logs/domain1.access.log main;  
index index.html;  
root  /var/www/domain1.com/htdocs;  
}  
# 旧的项目 对应 old.domain.com 域名  
server {  
listen 80;  
server_name   old.domain.com;  
location / {  
proxy_pass_header Server;
proxy_set_header Host $http_host;
proxy_redirect off;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Scheme $scheme;
# 转发给 81 端口的 lighttpd 处理  
proxy_pass      http://127.0.0.1:81;  
}  
}  
}