Eric W. (10):
Start Known Issues section in README
Allow binding to UNIX sockets relative to “~”
tests: do not trust (our correct use of) 1.9 encodings
gracefully die if working dir is invalid at fork
Add signal queueing for test reliability
Add unicorn_rails script for Rails 2.3.2
Documentation updates, prepare for 0.2.0
unicorn 0.2.0
unicorn v0.2.1, fix the Manifest
== Disclaimer
There are no known production instances of unicorn deployed
anywhere in the world. The original author of unicorn only has
one, internal, low-traffic Sinatra application deployed with it.
Maybe you’ll be the first guinea pig to test it in production.
Of course there is NO WARRANTY whatsoever if anything goes wrong,
but let us know and we’ll try our best to fix it.
There are no known production instances of unicorn deployed
anywhere in the world. The original author of unicorn only has
one, internal, low-traffic Sinatra application deployed with it.
Maybe you’ll be the first guinea pig to test it in production.
Of course there is NO WARRANTY whatsoever if anything goes wrong,
but let us know and we’ll try our best to fix it.
There are no known production instances of unicorn deployed
anywhere in the world. The original author of unicorn only has
one, internal, low-traffic Sinatra application deployed with it.
Maybe you’ll be the first guinea pig to test it in production.
Of course there is NO WARRANTY whatsoever if anything goes wrong,
but let us know and we’ll try our best to fix it.
Would that have to be a virgin guinea pig?
Nope, any guinea pig will do just fine.
I just made a Unicorn::App::ExecCgi Rack handler and then I made my cgit
instance run on it:
Yes, all that Ruby just to run a CGI executable written in C.
But that’s the only dynamic site that I can mess with right now,
so it’s either that or nothing.
Assuming the site is still up by the time I wake up tomorrow, I’ll
edit that disclaimer
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.