使用Nginx + unicorn搭建ruby on rails的生產環境
有三臺機器，操作系統都是CentOS 6.3 64位：其中172.16.9.100，安裝Nginx服務器；另外的兩臺172.16.9.101和172.16.9.102安裝unicorn，作為RoR的應用服務器。在這里先保證ruby及rails已經在101和102兩臺機器上配置好，這是前提。如何安裝Nginx及RoR的環境就不在這里說了，很多文章都介紹得很詳細。
這里假設項目在/var/www/demo_project文件夾中
在101上使用
gem install unicorn 命令安裝unicorn。
新建內容為以下的一個文件，需要進行修改的地方請看文件中的中文注釋，文件放置到/var/www/demo_project_unicorn.rb，這個文件是對這個項目的生產環境配置
# Sample verbose configuration file for Unicorn (not Rack) #This configuration file documents many features of Unicorn
that may not be needed for some applications. See
http://unicorn.bogomips.org/examples/unicorn.conf.minimal.rb
for a much simpler configuration file.
#
See http://unicorn.bogomips.org/Unicorn/Configurator.html for complete
documentation.
Use at least one worker per core if you're on a dedicated server,
more will usually help for short waits on databases/caches.
worker_processes 4
Since Unicorn is never exposed to outside clients, it does not need to
run on the standard HTTP port (80), there is no reason to start Unicorn
as root unless it's from system init scripts.
If running the master process as root and the workers as an unprivileged
user, do this to switch euid/egid in the workers (also chowns logs):
user "unprivileged_user", "unprivileged_group"
Help ensure your application will always spawn in the symlinked
"current" directory that Capistrano sets up.
working_directory "/var/www/demo_project" # available in 0.94.0+ 在這里修改為項目所在目錄
listen on both a Unix domain socket and a TCP port,
we use a shorter backlog for quicker failover when busy
listen "/var/tmp/.unicorn.sock", :backlog => 64 listen 19527, :tcp_nopush => true #端口號，NginX需要用到此端口號
nuke workers after 30 seconds instead of 60 seconds (the default)
timeout 120
feel free to point this anywhere accessible on the filesystem
pid "/usr/tmp/demo_project/pids/unicorn.pid" #pid文件的位置，可以自己設置，注意權限
By default, the Unicorn logger will write to stderr.
Additionally, ome applications/frameworks log to stderr or stdout,
so prevent them from going to /dev/null when daemonized here:
stderr_path "/usr/tmp/demo_project/log/unicorn.stderr.log" #錯誤日志的位置，自己設置，注意權限 stdout_path "/usr/tmp/demo_project/log/unicorn.stdout.log" #輸出日志的位置，自己設置，注意權限
combine Ruby 2.0.0dev or REE with "preload_app true" for memory savings
http://rubyenterpriseedition.com/faq.html#adapt_apps_for_cow
preload_app true GC.respond_to?(:copy_on_write_friendly=) and GC.copy_on_write_friendly = true
Enable this flag to have unicorn test client connections by writing the
beginning of the HTTP headers before calling the application. This
prevents calling the application for connections that have disconnected
while queued. This is only guaranteed to detect clients on the same
host unicorn runs on, and unlikely to detect disconnects even on a
fast LAN.
check_client_connection false
before_fork do |server, worker| # the following is highly recomended for Rails + "preload_app true" # as there's no need for the master process to hold a connection defined?(ActiveRecord::Base) and ActiveRecord::Base.connection.disconnect!
# The following is only recommended for memory/DB-constrained # installations. It is not needed if your system can house # twice as many worker_processes as you have configured. # # # This allows a new master process to incrementally # # phase out the old master process with SIGTTOU to avoid a # # thundering herd (especially in the "preload_app false" case) # # when doing a transparent upgrade. The last worker spawned # # will then kill off the old master process with a SIGQUIT. # old_pid = "#{server.config[:pid]}.oldbin" # if old_pid != server.pid # begin # sig = (worker.nr + 1) >= server.worker_processes ? :QUIT : :TTOU # Process.kill(sig, File.read(old_pid).to_i) # rescue Errno::ENOENT, Errno::ESRCH # end # end # # Throttle the master from forking too quickly by sleeping. Due # to the implementation of standard Unix signal handlers, this # helps (but does not completely) prevent identical, repeated signals # from being lost when the receiving process is busy. # sleep 1 end
after_fork do |server, worker| # per-process listener ports for debugging/admin/migrations # addr = "127.0.0.1:#{9293 + worker.nr}" # server.listen(addr, :tries => -1, :delay => 5, :tcp_nopush => true)
# the following is required for Rails + "preload_app true", defined?(ActiveRecord::Base) and ActiveRecord::Base.establish_connection
# if preload_app is true, then you may also want to check and # restart any other shared sockets/descriptors such as Memcached, # and Redis. TokyoCabinet file handles are safe to reuse # between any number of forked children (assuming your kernel # correctly implements pread()/pwrite() system calls) end</pre>
然后創建一個shell文件，內容如下，這個文件命名為/var/www/unicorn.sh
UNICORN=/usr/local/ruby/bin/unicorn_rails killall -9 unicorn_rails $UNICORN -c /var/www/demo_project_unicorn.rb -D -E production其中第一行，指明unicorn的安裝位置，unicorn安裝成功后，是和ruby，rails等可執行文件是在同一個文件夾中的。第二行，關閉unicorn_rails的進程。第三行，根據-c參數后的配置，在生產環境中啟動項目。執行這個文件就能啟動unicorn服務器。
另外的一臺主機102的配置，也與101相同。unicorn的配置也就完成了。下面開始NginX的配置
在/usr/local/nginx/conf/nginx.conf中添加如下的配置信息，具體意思見中文注釋
upstream demo_project_backend { #連接兩臺RoR unicorn服務器 server 172.16.9.101:19527; server 172.16.9.102:19527; }server { listen 80 default_server; servername ; return 403; }
server { listen 80; server_name www.demo_project.com demo_project.com; #access_log logs/host.access.log main; proxy_connect_timeout 500s; proxy_read_timeout 500s; proxy_send_timeout 500s; #將對的請求，轉到兩臺主機上 location / { root html; index index.html index.htm; proxy_pass http://demo_project_backend; } # redirect server error pages to the static page /50x.html # error_page 500 502 503 504 /50x.html; location = /50x.html { root html; }
}</pre>
來自：http://my.oschina.net/mogralee/blog/299890