Date | Commit message (Collapse) |
|
So says the project website and documentation
|
|
|
|
In short: upgrade to Rails 2.3.4 (or later)
ref: http://mid.gmane.org/20091014221552.GA30624@dcvr.yhbt.net
Note: the workaround described in the article above only made
the issue more subtle and we didn't notice them immediately.
|
|
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.
|
|
We hope to never require copyright assignment here...
|
|
It may have caused confusion that the licenses we're under
were incompatible with older Rubygems which is not the case.
|
|
This allows `gem check -t unicorn` to work. The rest of
the tests run with GNU make but I don't have the patience
to get them working with pure-Ruby since I can't stand
running those tests sequentially anyways.
|
|
Not sure if anybody runs tests with Rubygems directly
(instead of unpacking the source tree, but it's there)
|
|
"licenses=" is not in older Rubygems and some organizations
are still stuck on those...
|
|
|
|
* Manifest/CHANGELOG can be maintainance is painful.
I really hate having those in the source tree when
I have a version control system that already:
1) encourages me to make meaningful commits
2) is highly scriptable for generating manifests/changelogs
* hand-rolled gemspec allows more control for specifying
pre-release gem versions
* Less magic over what the `rubyforge` command does, being
able to spawn $VISUAL on changelogs/release notes and make
edits on them is nice.
Additionally I still strongly prefer GNU make over Rake for many
tasks since it offers better parallelization and some things are
easier *for me* in shell than Ruby.
|