Displaying 20 results from an estimated 1000 matches similar to: "unicorn 0.94.0 - small fixes and new features"
2011 Apr 19
0
unicorn 3.6.0 release soon
Mainly small fixes, improvements, and workarounds for fork() issues
with pseudo-random number generators shipped with Ruby (Kernel#rand,
OpenSSL::Random (used by SecureRandom and also by Rails).
If there are any other fixes/improvements that could be useful let us
know. I think this is nearing the end of the line for the 3.x series
which will then go into maintenance mode. I''m looking
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
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
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.
2010 Oct 02
2
Unicorn doesn't reload the app after the HUP signal
Hi folks, I''ve experimented a problem while deploying my app, I''ve
sent the HUP signal to the master process, I''ve checked everything is
ok: new master and workers are spawned and the old ones are
killed(I''ve checked the PIDs), but the new code deployed isn''t
reflected in the living site, so I''ve to stop and start again unicorn
in order to see
2011 Jun 16
7
[PATCH] replace fchmod()-based heartbeat with raindrops
This means we no longer waste an extra file descriptor per
worker process in the master. Now there''s no need to set a
higher file descriptor limit for systems running >= 1024
workers.
---
I just pushed this out to git://bogomips.org/unicorn.git and it''ll
be in Unicorn 4.x.
The subset of raindrops used by Unicorn should work on all machines
with mmap(2) +
2009 Feb 11
16
Unicorn: UNIX+localhost/LAN-only Mongrel fork
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,
2012 Jul 19
5
Detecting unicorn / defining after_fork after master startup
Hey everyone,
Working on an engine for rails that needs specialized behavior with
forking and I had a couple questions.
1. What is the best way to determine whether the app is indeed running
inside a unicorn server?
Most of the attempts I can find to detect check to see if the main
modules for Unicorn are defined, but this really only checks to see
that Unicorn is present, not that you are
2012 Dec 04
2
403 Forbidden from nginx when unicorn started in debug mode
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 =
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
2012 Oct 12
3
[PATCH] explicitly use escaped minus in man pages
---
man/man1/unicorn.1 | 32 ++++++++++++++++----------------
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
2012 May 09
5
Unicorn doesn't play nice with Capistrano deployment?
I am having issues when using unicorn with a Capistrano deployment.
>From what I have been able to understand Capistrano uses a scheme in
wich every release is deployed inside the releases directory under a
unique name and if the transaction was successful, creates a symlink
named current that will point to that release.
So I end up with a deployment directory such as:
2012 Aug 31
1
after_fork - ActiveRecord::AdapterNotSpecified
Hi all,
I''m fighting with the after_fork hook and my sinatra application. The Sinatra app is using active_record,
In my unciron.rb file I''m using
preload_app true
after_fork do |server, worker|
? defined?(ActiveRecord::Base) and
??? ActiveRecord::Base.establish_connection
End
but I always get the error:
ERROR -- : ActiveRecord::AdapterNotSpecified
2013 May 20
2
Unicorn + RUnit Rails Not Killing Old Master
Hi,
I''m deploying Unicorn on a Rails application with RUnit. Technically
I''m using Chef''s deployment tools, if any of you are familiar with it
(https://github.com/opscode-cookbooks/application_ruby) but to be clear
they aren''t doing anything magical, so this is purely an issue with
RUnit and Unicorn.
The TL;DR of the following post, which has lots of
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
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 Nov 09
2
AMQP and Unicorn (mq gem)
Hi all,
I''m having issues with Unicorn and connecting to
RabbitMQ using the tmm1-amqp gem.
I''ve tried lots of approaches.
The classic initializer with Thread.new { EM.run }
for the Rails app and even tried using
the Qusion library.
(https://github.com/danielsdeleo/qusion)
I''ve made a simple mod to Qusion for it to monkey patch
unicorn too.
The code looks
2009 Oct 02
0
[PATCH] configurator: update some migration examples
We now give an example of how a before_fork hook can be used
to incrementally migrate off the old code base without hitting
a thundering herd (especially in the "preload_app false") case.
Also comment on the per-worker listen usage in the RDoc, not
just a hidden comment.
---
I just pushed this out earlier, this example was inspired by Chris
Wanstrath''s before_fork hook but
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
2011 Sep 30
3
Multiple rack applications on the same server with unicorn
If I''m running two rails apps on the same server using Unicorn, I have
to run two instances of Unicorn, right?
If so, then here''s a place where passenger might win in terms of
memory use, as the rails code will be loaded into memory twice, right?
I''m still probably going with Unicorn, but just exploring this first.
Thanks,
John