search for: rackup

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:

Hi, guys, I got the below error message when i typed this command in terminal "rackup config.ru" , the file config.ru is rails ''s configuration file. You have already activated rack 1.3.2, but your Gemfile requires rack 1.2.3. Consider using bundle exec. (Gem::LoadError) So, how should i do , thanks a lot. -- You received this message because you are subscribed t...

...---------------- man/man1/unicorn_rails.1 | 34 +++++++++++++++++----------------- 2 files changed, 33 insertions(+), 33 deletions(-) diff --git a/man/man1/unicorn.1 b/man/man1/unicorn.1 index 0b496af..749272a 100644 --- a/man/man1/unicorn.1 +++ b/man/man1/unicorn.1 @@ -4,7 +4,7 @@ unicorn - a rackup-like command to launch the Unicorn HTTP server .SH SYNOPSIS .PP -unicorn [-c CONFIG_FILE] [-E RACK_ENV] [-D] [RACKUP_FILE] +unicorn [\-c CONFIG_FILE] [\-E RACK_ENV] [\-D] [RACKUP_FILE] .SH DESCRIPTION .PP A rackup(1)-like command to launch Rack applications using Unicorn. @@ -26,7 +26,7 @@ Emb...

Has anybody succeed in getting Rails 3 to work in production? I am trying with Apache 2.2 and Passenger 2.2.12 but no luck. If you have got Rails three to work in production on any server with any set up could you please post the details (howto?) or a link to where such information can be found. All input gratefully received. Paul Thompson -- You received this message because you are

...using Rails.application or MyAppName::Application object to serve a Rails application. There''s another thing. Just after the text above you can find this: rails server does the basic job of creating a Rack::Builder object and starting the webserver. This is Rails’ equivalent of Rack’s rackup script. Which is not true, at least it doesn''t do it directly, what it does is: 1. It creates a class: class Server < ::Rack::Server 2. The Server#start method calls "super" 3. Rack creates the Rack::Builder object am I wrong? So, what do you think about those changes? T...

...atest rubinius.git[1], Rubinius support is nearly complete as well. Under Rubinius, signals may corrupt responses as they''re being written to the socket, but that should be fixable transparently to us[4]. Support for the hardly used, hardly documented[2] embedded command-line switches in rackup config (.ru) files is is also broken under Rubinius. The recently-released Rack 1.2.1 introduced no compatiblity issues[3] in core Unicorn. We remain compatible with all Rack releases starting with 0.9.1 (and possibly before). [1] tested with Rubinius upstream commit cf4a5a759234faa3f7d8a92d68fa...

Installing from RubyGems.org: gem install --pre unicorn >From db919d18e01f6b2339915cbd057fba9dc040988b Mon Sep 17 00:00:00 2001 From: Eric Wong <normalperson at yhbt.net> Date: Tue, 29 Jan 2013 21:02:55 +0000 Subject: [PATCH] unicorn 4.6.0pre1 - hijacking support This pre-release adds hijacking support for Rack 1.5 users. See Rack documentation for more information about hijacking.

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 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,

...cgi.rb & mongrel.rb). bin/camping does now only provide WEBrick, Mongrel and console-support and should only be used in development. It uses Rack::ShowExceptions to catch error outside the app and I''ve also written a middleware for faking X-Sendfile. For production you should create a rackup-file or setup Rack in some other way: #!/usr/bin/env rackup # Auto-detects CGI & FastCGI # Start mongrel with: ./blog.ru -s mongrel -p 3301 require ''blog'' Blog.create run Blog Some notes: * Branch: http://github.com/judofyr/camping/commits/rack * You have to rena...

For example, I have a webapp that handles /welcome. Does unicorn support to mount the entire webapp at /prefix so request to /prefix/welcome are?handled?

I''m migrating an old Rails App to a new server, I think I''ve got most of my issues worked out so far. But.... When I run script/server --trace in the app I get the following output... and I have no clue what to do or even where to look... Any guidance or assistance would be greatly appreciated. script/server --trace => Booting WEBrick... server: invalid option: --trace

...passenger to new 2.2.7 version and my app started to work incorrectly, because it lauched in development environment. I tried to set "RailsEnv production", "RackEnv production" at my httpd.conf, but this dont work. So, maybe somenthing wrong with my config.ru? #!/usr/bin/env rackup -p3000 require "config/environment" use Rails::Rack::LogTailer use Rack::AssetPath # <- my own middleware use Rails::Rack::Static run ActionController::Dispatcher.new What is wrong? Where can i read about customizing config.ru for production environments? Thank you -- You received...

...Unicorn::Util.reopen_logs logger.info "master done reopening logs" - kill_each_worker(:USR1) + soft_kill_each_worker(:USR1) when :USR2 # exec binary, stay alive in case something went wrong reexec when :WINCH if Unicorn::Configurator::RACKUP[:daemonized] respawn = false logger.info "gracefully stopping all workers" - kill_each_worker(:QUIT) + soft_kill_each_worker(:QUIT) self.worker_processes = 0 else logger.info "SIGWINCH ignored because we''...

...SX), but when deploying to production on Heroku, it fails silently (no backtrace, no error detail). Log looks like: Starting process with command `bundle exec unicorn start -p 6069 -c ./config/unicorn.rb` /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:634:in `parse_rackup_file'': rackup file (start) not readable (ArgumentError) from /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:77:in `reload'' from /app/vendor/bundle/ruby/1.9.1/gems/unicorn-4.6.2/lib/unicorn/configurator.rb:68:in `initialize'' from /app/ve...

Hi All, as I can see on https://github.com/defunkt/unicorn/blob/master/lib/unicorn.rb#L53 the?Rack::CommonLogger used only in development env and in weird evn called "deployment". Any chance to add "production" to this case? Serg Podtynnyi

Hi, I''m trying to use unicorn in a test deployment of a Rails app that uses Mongoid, so Activerecord isn''t included in the app. When I start unicorn through Capistrano though, the stderr log fills up endlessly with identical ActiveRecord-related errors: I, [2012-12-05T04:19:25.375952 #5096] INFO -- : Refreshing Gem list I, [2012-12-05T04:19:32.941249 #5096] INFO -- :