unicorn

I am trying since 2 days to deploy on my vps (Ubuntu 12.04 Server (64 bits)) using : ruby (1.9.3-rc1), rails, capistrano, nginx and unicorn. I also follow railscast tutorial from Ryan Bates showing how to deploy on VPS from scratch. Actualy the cap deploy:cold command seems to work fine (as all the others) but when i try to go on my url i fall on "We're sorry but something went wront" => The default error page from Rails. In my production logs i get : Migrating to CreateQuestionAnswers (20130317152603) Migrating to CreateRegions (20130502212531) Migrating to AddRegionIdToSection

I have a Rails 3.1 app running in production using Nginx and Unicorn. And for some reason, my custom 404 and 500 html error pages are not showing. Instead I'm getting the actual error message ("Routing Error", for example). In my production.rb file, I have config.consider_all_requests_local = false And on the same server with a nearly identical configuration, I have a 'staging' site that works just fine. The only difference, as far as I can tell, is that the production one has SSL while the staging does not. Here is the Nginx config for the production app: upstream unicorn_myapp_prod { server

We've been using unicorn to deploy our application. Everything went fine except for the production.log file, which turned out to be unreadable because the way unicorn was designed. Every instance of unicorn wrote to the same file, causing all the lines spaghetti'ed together. So is there a way to tell the logger to log independently across multiple unicorn instances? edit your unicorn.conf.rb , and change the after_fork block to something like: after_fork do |server, worker| filepath = "#{Rails.root}/log/#{Rails.env}.#{worker.nr}.log" Rails.logger = Logger.new(filepath, File::WRONLY | File: