similar to: Multiple rack applications on the same server with unicorn

>From dcd47a609f4489bb37ce33ea1ce975bb2b3ab160 Mon Sep 17 00:00:00 2001 From: Hongli Lai (Phusion) <hongli at phusion.nl> Date: Mon, 6 Jun 2011 13:36:57 +0200 Subject: [PATCH] Document the method for building the Unicorn gem. Signed-off-by: Hongli Lai (Phusion) <hongli at phusion.nl> --- HACKING | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git

Does unicorn work like phusion in that it automatically forks based on traffic levels? Or is that what thin does also? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org

On a debian production server and my os x development mcahine, there is a script at /usr/local/bin/mongrel_rails On an ubuntu 7.1 machine, this script appears at /var/lib/gems/1.8/bin/mongrel_rails mongrel was installed using gem in all cases. What is the cause of the discrepancy? Thanks, John -- John Joseph Bachir http://lyceum.ibiblio.org http://blog.johnjosephbachir.org

Hi all, I''ve pushed the following patch out go git://git.bogomips.org/unicorn along with a few other Rails-related test updates. This is more of a shotgun fix (but less code is better :) since I haven''t been able to reproduce the brokeness people have been seeing with "unicorn_rails" and Rails 3 betas. Even though "unicorn" works perfectly well for Rails3,

Hi I''ve migrated from Passenger to Unicorn about a week ago. It''s great. Great transparency and management, thanks for this great software! A few of my Rails applications start background jobs using Kernel#fork. Of course, the ActiveRecord connections are closed and reopened again in the parent and child processes. The child process also does its job. Unfortunately, it seems

Hi, A couple days ago, I was trying to run Unicorn for Ramaze, and found that `Unicorn.run'' didn''t share the same interface with other Rack handlers, i.e. `options[:Host]'' and `options[:Port]'' Because of this, I can''t just use: Rack::Handler.register(''unicorn'', ''Unicorn'') And invoke this:

Has anyone seen anything like this before? I can get it to happen all the time if I issue a HEAD request, but it only happens very intermittently on GET requests. I''m using Ruby 1.9.2p180. Any ideas on where to start debugging? 204.93.223.151, 10.195.114.81 - - [11/Aug/2011 21:03:50] "GET / HTTP/1.0" 200 37902 0.5316 app error: Content-Length header was 37902, but should be

Hello to everybody. I making shared hosting for rails and rack applications. For app. server i userd phusion passenger, but after some issues with that, want to migrate to unicorn. Is there any way to make unicorn stop all workers and start them on first request? It''ll be really great to have this opportunity. >No subscription is needed to post to the mailing list, let us know

I''m using god* to monitor my mongrels. God looks at pid files to know the status of the cluster. It seems as though mongrel does not write a pid file until it has loaded the entire rails/project environment, which in my case, takes upwards of 90 seconds. Meanwhile, god is freaking out because it thinks that there aren''t mongrels running, and it tries to start them. Thankfully I

Hi folks. Using mongrel_rails and the mongrel_cluster capistrano recipes, I often encounter a situation where some of the mongrel processes don''t die in time to be restarted. The output of capistrano will tell me something like "mongrel on port 8001 is already up", but that''s only because capistrano/mongrel_rails failed to take it down in the first place. The solution

Hi, I wanted to try out Edge Rails 3 today and hit a serious problem trying to run mongrel. script/rails server mongrel just hangs. Interrupting and looking up the spot of the lockup revealed $LOAD_PATH.unshift ''projects/mongrel_experimental/lib/'' Mongrel::Gems.require ''mongrel_experimental'', ">=#{Mongrel::Const::MONGREL_VERSION}" at the bottom

Hello all, Last week, I finally decided to put into motion some ideas I''ve been kicking around for a year in my head since last year... Basically I don''t want to have to deal with threads or support platforms that rely on or encourage threads. Especially given MRI 1.9 where kernel threads are more difficult to debug than green ones. Given the limited scope of this project,

After much fiddling and googling, it seems to me that Mongrel, even the 1.2.0pre2 release is not compatible with Rails 3 -- is that true? When I start up a new Rails 3 project (i.e. one fresh after a `rails new` command), mongrel appears to start (creates a pid file, and reports no errors on the CLI), but the app does not load in the browser and I find this in the mongrel.log

Hello all, I''m wondering if you deploy nginx: 1) on the same machine that runs unicorn (exclusively proxying to that) 2) on a different machine that doesn''t run unicorn 3) both, nginx could forward to either to localhost or another host on the same LAN And of course, the reason(s) you chose what you chose. I''m inclined to believe many folks are on 1) simply

I would love to see a timestamp in each line of unicorn stderr and stdout logs. Has this been considered? Thanks. Best, alex sharp

I am using nginx with unicorn as a reverse proxy. Has been fantastic, but needed to look through some code for first time. Using ruby 1.9.3p194 with rails 3.2.9, development mode with ssl enabled, I start unicorn with -d ...and it does not get served up by nginx. Any ideas, or more information needed? Thanks! Jet Below is my unicorn.rb for developent: # config/unicorn.rb env =

hey, i am a big unicorn fan -- i have been running it in production since late 2010, and it is happily handling (literally) billions of backend requests for a popular facebook game. i also <3 unicorns in general ..... so i decided to make an awesome t- shirt, sporting the "Angry Unicorn" that you may remember from github error pages. i hope some of you might like it as well:

Hi all, I''ve committed support to Unicorn for old versions of Rails that didn''t support Rack. I think it could be useful for Mongrel 2 (or any other server) as well: http://git.bogomips.org/cgit/unicorn.git/commit/?id=0b095ea72 [1] or just fetch/clone git://git.bogomips.org/unicorn.git The bin/unicorn_rails code is itself a mess, but cleaning it up is on my ever growing

Hi, For one of our apps we switched to unicorn from mongrel. The unicorn server use to run behind an apache with timeout of 300sec, as sometime the customer may do a large file upload. After we made the switch we started getting lots of Unicorn::ClientShutdown occurred in photos#flash_upload bytes_read=2762663 (pr some other number) We were not able to recreate it in our tests, but support was

Hi, I''m currently giving Nginx + Unicorn a try, to eventually replace Apache + Passenger. So far so good. I have a Rails 3.2.5 app behind Unicorn, itself behind Nginx. In this Rails app, I have set page caching for some resources. They are created in Rails.root/public/ to be directly available to Nginx. When I first hit such a page, the static cache file is not present, so the Rails