Displaying 20 results from an estimated 4000 matches similar to: "[PATCH] explicitly use escaped minus in man pages"
2013 Jan 29
2
unicorn 4.6.0pre1 - hijacking support!
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.
2009 Nov 05
0
unicorn 0.94.0 - small fixes and new features
Unicorn is a HTTP server for Rack applications designed to only serve
fast clients on low-latency, high-bandwidth connections and take
advantage of features in Unix/Unix-like kernels. Slow clients should
only be served by placing a reverse proxy capable of fully buffering
both the the request and response in between Unicorn and slow clients.
* http://unicorn.bogomips.org/
* mongrel-unicorn at
2012 Dec 05
3
Fwd: Issue starting unicorn with non-ActiveRecord Rails app
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 -- :
2010 Jun 04
8
unicorn_rails cleanup (possible fix for Rails3) pushed
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,
2010 Feb 18
4
Rails 3 "RAILS_ENV not defined by config/boot" error
I''m running unicorn and unicorn-rails 0.96.1 and the latest Rails 3
beta gem. ?Firing up unicorn_rails spews "RAILS_ENV not defined by
config/boot". ?I know this is likely a result of RAILS_ROOT being
deprecated?in Rails 3 but I can''t seem to config my way around it.
I''m sure other people must have run into this before. ?Is there a
quick fix?
Thanks
2010 May 28
4
unicorn failing to start
Hi,
i''m trying to start up unicorn_rails with a rails 3 beta3 project. All I
can get out of it is this:
I, [2010-05-28T08:54:45.770957 #17852] INFO -- : reaped
#<Process::Status: pid 17854 exit 1> worker=0
I, [2010-05-28T08:54:45.771200 #17852] INFO -- : worker=0 spawning...
I, [2010-05-28T08:54:45.774049 #17858] INFO -- : worker=0 spawned pid=17858
I,
2011 May 19
2
unicorn doesn't restart properly after cap deploy (not using Bundler)
Hey guys,
I''m sending USR2 to unicorn after cap deploy, and the old master is
getting replaced by a new master that doesn''t work.
Here are some similar threads I found ...
http://rubyforge.org/pipermail/mongrel-unicorn/2010-October/000733.html
http://rubyforge.org/pipermail/mongrel-unicorn/2010-October/000717.html
I''m not using Bundler, and I have working_directory
2011 Aug 12
16
Rack content-length Rack::Lint::LintErrors errors with unicorn
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
2011 Sep 06
1
Workers getting broken after some time
I have strange error that happens after couple of hours. Some instances
start to respond on any request with status code 500. Log file
unicorn.stderr.log gets populated with this error:
app error: undefined method `each'' for nil:NilClass (NoMethodError)
/usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.2/lib/rack/utils.rb:267:in
`initialize''
2010 Mar 01
0
unicorn 0.97.0 - polishing and cleaning up
Unicorn is an HTTP server for Rack applications designed to only serve
fast clients on low-latency, high-bandwidth connections and take
advantage of features in Unix/Unix-like kernels. Slow clients should
only be served by placing a reverse proxy capable of fully buffering
both the the request and response in between Unicorn and slow clients.
* http://unicorn.bogomips.org/
* mongrel-unicorn at
2009 Oct 13
7
Unicorn Nginx Issue
I''ve setup nginx with this
server {
listen 80;
server_name unicorn.local;
location / {
proxy_pass http://unicorn;
}
}
upstream unicorn {
server unix:/Users/mattmongeau/projects/test/unicorn/tmp/sockets/unicorn.sock;
}
When I run unicorn_rails -c config/unicorn.rb -E development I can
access the application just fine on unicorn.local
When I run unicorn_rails -c
2010 Sep 07
1
unicorn_rails and rails 2.3.8
First off, I love unicorn. Thanks to all who have worked on it.
For the first time, I am trying to run a rails 2.3 app with unicorn. I don''t understand what is not set correctly. I have rails 2.3.8 and dependencies installed. I am sure it is something simple.... See output below.
Much thanks!
Matt
config/environment.rb
...
RAILS_GEM_VERSION = ''2.3.8'' unless defined?
2010 Jun 17
3
unicorn 1.0.0 - yes, this is a real project
Unicorn is an HTTP server for Rack applications designed to only serve
fast clients on low-latency, high-bandwidth connections and take
advantage of features in Unix/Unix-like kernels. Slow clients should
only be served by placing a reverse proxy capable of fully buffering
both the the request and response in between Unicorn and slow clients.
* http://unicorn.bogomips.org/
* mongrel-unicorn at
2013 May 25
1
Silent Failure when starting Unicorn on Heroku
Switched my RoR (3.1.3, 1.9.2) app from Thin to Unicorn (4.6.2). It ran
fine in development
(Mac OSX), 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
2011 Jun 06
2
[PATCH] Document the method for building the Unicorn gem
>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
2009 Mar 23
0
OldRails Rack handler added to Unicorn
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
2010 Jun 02
8
Read error: #<TypeError: can't modify frozen string> raised from HttpParser
Hey guys,
Started running unicorn in a production server like two weeks ago.
It''s been running smoothly, but looking at the logs found 44
exceptions like this:
E, [2010-06-02T16:17:15.117071 #22680] ERROR -- : Read error:
#<TypeError: can''t modify frozen string>
E, [2010-06-02T16:17:15.117270 #22680] ERROR -- :
2012 Dec 07
3
Ubuntu upstart
I cannot find any good example of a unicorn upstart task that works
properly for the following:
* Upstart will restart if unicorn dies
* Can send USR2 signal to unicorn to do a no downtime deploys
* Able to stop upstart job, even after a deploy
I have tried the following:
expect fork
respawn
setuid www-data
chdir /var/www/app/current
exec bundle exec unicorn_rails -E production -c
2013 Mar 20
2
Problem With Unicorn
Hello All,
I deployed my application in the local server and i''m using unicorn and
nginx. I tried to run ''bundle exec unicorn_rails'' but it is showing ''ERROR:
Gem bundler is not installed, run `gem install bundler` first.''. even if I
run gem install bundler the bundler getting installed, But it is showing
the same error again i.e. Gem bundler is not
2013 Dec 09
2
[PATCH] rework master-to-worker signaling to use a pipe
Signaling using normal kill(2) is preserved, but the master now
prefers to signal workers using a pipe rather than kill(2).
Non-graceful signals (:TERM/:KILL) are still sent using kill(2),
as they ask for immediate shutdown.
This change is necessary to avoid triggering the ubf (unblocking
function) for rb_thread_call_without_gvl (and similar) functions
extensions. Most notably, this fixes