unicorn

问题 I'm playing around with a tutorial which uses unicorn and rails. I'm completely new to rails and for the purpose of the tutorial all I've done for the project is bundle exec rails new rails-starter with no further app modifications. When I run bundle exec unicorn -c config/unicorn.rb -E production I get the message in the browser: The page you were looking for doesn't exist. You may have mistyped the address or the page may have moved. The log shows: ActionController::RoutingError (No route

问题 I'm using Rails 4.0.0, Ruby 2.3 and Unicorn. My app was working perfectly until the day I tried to add a nem gem in my Gemfile. Everything's working like a charm locally, but when I deploy to DO using Capistrano, I get stuck in a loop with the error: E, [2016-09-26T11:40:29.801388 #24545] ERROR -- : reaped #<Process::Status: pid 4280 exit 1> worker=0 I, [2016-09-26T11:40:29.802952 #4287] INFO -- : Refreshing Gem list /home/deployer/apps/my_app/shared/bundle/ruby/2.3.0/gems/activesupport-4.0.0

问题 I've setup unicorn in rails 3.1 and http streaming works until I enable Rack::Deflater. I've tried both with and without use Rack::Chunked. In curl I can see my response while in chrome I get the following errror: ERR_INVALID_CHUNKED_ENCODING The result is same in other browsers (firefox, safari) and between development (osx) and production (heroku). config.ru: require ::File.expand_path('../config/environment', __FILE__) use Rack::Chunked use Rack::Deflater run Site::Application unicorn.rb:

问题 Gitlab 6.0 was released yesterday. I am curious to know why they switched to Unicorn from Puma. Versions prior to 5 were using Unicorn. I thought switch to Puma was for the better. Is there a technical reason for this switch? 回答1: GitLab B.V. CEO here, I agree with Hongli his comment that "If there are issues then they are likely in Gitlab's code.". We tried to fix them but GitLab is one of the largest open source Rails applications and the issues where hard to reproduce. So in the end we

问题 How can I make each unicorn worker of my Rails application writting in a different log file ? The why : problem of mixed log files... In its default configuration, Rails will write its log messages to a single log file: log/<environment>.log . Unicorn workers will write to the same log file at once, the messages can get mixed up. This is a problem when request-log-analyzer parses a log file. An example: Processing Controller1#action1 ... Processing Controller2#action2 ... Completed in 100ms..

问题 i am trying to add unicorn to one of my rails apps on heroku - i've added the unicorn config file and the unicorm gem to the gemfile but when i try to bundle install on my windows dev machine i get: An error occurred while installing kgio (2.8.0), and Bundler cannot continue. i tried 'gem install kgio -v "2.8.0' and get similar errors. i am running ruby 1.9.3p125. One of the posts said something about it only running in a Unix [nonwindows] environment. i guess i really only need it running on

问题 A new Rails project's Gemfile shows: # Use unicorn as the app server gem 'unicorn' rails s --help shows: Usage: rails server [mongrel, thin, etc] [options] Yet, doing: rails s unicorn I get: /Users/patrick/.rvm/gems/ruby-1.9.3-head@keynote/gems/rack-1.4.5/lib/rack/handler.rb:63:in `require': cannot load such file -- rack/handler/unicorn (LoadError) from /Users/patrick/.rvm/gems/ruby-1.9.3-head@keynote/gems/rack-1.4.5/lib/rack/handler.rb:63:in `try_require' from /Users/patrick/.rvm/gems/ruby-1

问题 I was trying to use Thin app server and had one issue. When nginx proxies the request to Thin (or Unicorn) using proxy_pass http://my_app_upstream; the application receives the modified URL sent by nginx ( http://my_app_upstream ). What I want is to pass the original URL and the original request from client with no modification as the app relies heavily on it. The nginx' doc says: If it is necessary to transmit URI in the unprocessed form then directive proxy_pass should be used without URI

问题 I have a single rails app running on a Rackspace VPS. The stack is rails3 + unicorn + nginx + mysql. There is a primary domain that sends traffic directly to the unicorn socket using proxy_pass. I have a new engine developed that's mounted under /digital . Right now, people can interact with that engine via http://primarydomain.com/digital. I want to host a new domain that forwards requests directly to /digital ; not to the root engine. So for instance, the following requests would yield

问题 I've deployed a Rails app to a VPS server, and I'm using the Nginx/Unicorn combo, everything works fine, except that for some reason beyond my understanding, the Omniauth callbacks redirect wrong, ie. http://unicorn/users/auth/linkedin/callback?oauth_token=95218ed3-b426-45ab-b022-693d2a2447cb&oauth_verifier=25955 it should instead be: http://my-real-domain.com/users/auth/linkedin/callback?oauth_token=95218ed3-b426-45ab-b022-693d2a2447cb&oauth_verifier=25955 What's wrong? why is the callback