Date | Commit message (Collapse) |
|
... And make the gemspec do minor un-RDoc-ing
|
|
It makes the HTML page too big and busy.
|
|
|
|
Either people are actually using it or somebody is running a
script to download gems off gemcutter in a loop... I suspect
the former...
|
|
|
|
Nobody really uses or cares for them anyways
|
|
So says the project website and documentation
|
|
Grammar na^H^Hexperts please correct us again if we're wrong.
|
|
|
|
Mailman is now configured to munge Reply-To: to point back to
the mailing list. This might make things easier for folks
on low traffic mailing lists like ours.
|
|
While Unicorn is one of very many Unix-only, pre-forking, shared
socket servers in existence, and Unicorn is _definitely_ not the
only server that only works *well* with fast clients, either.
But as far as we know, Unicorn is the first (and so far only)
server that emphasizes only working well with fast clients.
|
|
Still pretty rare, though.
|
|
|
|
We hope to never require copyright assignment here...
|
|
The >= 0.90.x series has been working out pretty well so far
with only a few minor bug fixes in between, so it'll be less
confusing.
|
|
This deserves to be a separate document and easier to find/edit.
|
|
|
|
Small fixes and documentation are the focus of this release.
James Golick reported and helped me track down a bug that caused
SIGHUP to drop the default listener (0.0.0.0:8080) if and only
if listeners were completely unspecified in both the
command-line and Unicorn config file. The Unicorn config file
remains the recommended option for specifying listeners as it
allows fine-tuning of the :backlog, :rcvbuf, :sndbuf,
:tcp_nopush, and :tcp_nodelay options.
There are some documentation (and resulting website)
improvements. setup.rb users will notice the new section 1
manpages for `unicorn` and `unicorn_rails`, Rubygems users
will have to install manpages manually or use the website.
The HTTP parser got a 3rd-party code review which resulted in
some cleanups and one insignificant bugfix as a result.
Additionally, the HTTP parser compiles, runs and passes unit
tests under Rubinius. The pure-Ruby parts still do not work yet
and we currently lack the resources/interest to pursue this
further but help will be gladly accepted.
The website now has an Atom feed for new release announcements.
Those unfamiliar with Atom or HTTP may finger unicorn@bogomips.org
for the latest announcements.
|
|
We're expanding our target audience to folks that do not use
HTTP (yet).
|
|
Note that Rubinius itself is still under heavy development, so
things we fix may break again. The pure-Ruby parts of Unicorn
don't even work properly on Rubinius.
|
|
|
|
* Documented Unicorn::HttpParser API methods
* Keep GPL2 (COPYING) as-is without RDoc formatting.
* The auto-generated index.html is stupid, replace it with
README which looks saner.
|
|
|
|
|
|
|
|
|
|
|
|
While we're at it remove the Windows-centric comment for
folks who can't get a C compiler and put in something useful
for the Red Hat/Debian crowd where splitting packages is all
the rage.
|
|
|
|
Older Sinatra would blindly try to run Mongrel or Thin at_exit.
This causes strange behavior to happen when Unicorn workers are
exited.
|
|
|
|
|
|
Copy and pasting from the RDoc web page and passing
"\342\200\224config-file" to the command-line does not work.
|
|
Given the amount of changes we've made to Mongrel,
"Solid Mongrel code base" doesn't seem appropriate.
Also try to clarify a few wording issues.
|
|
Reword and expand a bit
|
|
|
|
This resurrects old code from Mongrel to wrap the Rails
Dispatcher for older versions of Rails. It seems that
Rails >= 2.2.0 support Rack, but only >=2.3 requires it.
I'd like to support Rails 1.2.x for a while, too.
|
|
I'm trying hard not to scare potential users away,
maybe I'll hand out lollipops or something...
|
|
|
|
|
|
Some other frameworks may also have code reloading issues.
Since code reloading is mainly for development mode and Unicorn
is capable of replacing the running executable without any
dropping connections, broken code reloaders aren't worth
fixing from our code...
|
|
Reformat README to avoid preformatted text.
Document signal handling in SIGNALS.
Split out DESIGN, it's probably not as useful to end-users
Update CONTRIBUTORS
LICENSE: copyright is for me (Eric Wong), not Zed since this
is a Mongrel fork.
|
|
|
|
|
|
Tempfile reuse was over-engineered and the problem was not
nearly as big a problem as initially thought.
Additionally, it could lead to a subtle bug in an applications
that link(2)s or rename(2)s the temporary file to a permanent
location _without_ closing it after the request is done.
Applications that suffer from the problem of directory bloat are
still free to modify ENV['TMPDIR'] to influence the creation of
Tempfiles.
|
|
|
|
|
|
Avoid conflicting with existing Mongrel libraries since
we'll be incompatible and break things w/o disrupting
Mongrel installations.
|
|
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@798 19e92222-5c0b-0410-8929-a290d50e31e9
|
|
git-svn-id: svn+ssh://rubyforge.org/var/svn/mongrel/trunk@420 19e92222-5c0b-0410-8929-a290d50e31e9
|