サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ノーベル賞
mongrel.rubyforge.org
Apache Best Practice Deployment By Charles Brian Quinn The preferred setup (for now) is to put Mongrel behind an Apache 2.2.x server running mod_proxy_balancer. Apache is a proven web server, runs half the Internet, and is a pain to configure. These instructions should get you started, but refer to the Apache folks for anything more complex or weird. When you're just starting out, don't bother
How Many Mongrel Instances Should I Run? There is no set number that is "best" since that depends on factors like the type of application, server hardware, how dynamic the appication is, etc. I've found that 8-12 mongrel processes per CPU is about right, but I determined this by starting with 1 and then doing the following: Baseline Your Server Pick a URL to a small file that is running on your ap
Using Mongrel Cluster by Austin Godber Mongrel_cluster is a GemPlugin that wrappers the mongrel HTTP server and simplifies the deployment of webapps using a cluster of mongrel servers. Mongrel_cluster will conveniently configure and control several mongrel servers, or groups of mongrel servers, which are then load balanced using a reverse proxy solution. Typical load balancing reverse proxies i
What is Mongrel? Mongrel is a fast HTTP library and server for Ruby that is intended for hosting Ruby web applications of any kind using plain HTTP rather than FastCGI or SCGI. It is framework agnostic and already supports Ruby On Rails, Og+Nitro, Camping, and IOWA frameworks. Mongrel was originally written by Zed A. Shaw. It is licensed under the Ruby License. Getting Started The easiest way to g
このページを最初にブックマークしてみませんか?
『Mongrel - Trac』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く