Date | Commit message (Collapse) |
|
Because nobody has time to read about all the options Rainbows!
provides. yahns is basically XEpollThreadPool, with minor
improvements which weren't easily supportable with other
concurrency options.
|
|
wrongdoc was difficult to maintain because of the tidy-ffi
dependency and the HTML5 changes in Darkfish could not be
handled well by Tidy.
olddoc is superior as it generates leaner HTML which loads faster,
requires less scrolling and less processing power to render.
Aesthetic comparisons are subjective of course but completely
unimportant compared to speed and accessibility.
The presence of images and CSS on the old (Darkfish-based) site
probably set unreasonable expectations as to my ability and
willingness to view such things. No more, the new website is
entirely simple HTML which renders well with even the wimpiest
browser (hell, olddoc even tries to generate readable raw HTML).
|
|
The --sanitize-html option is gone nowadays.
|
|
Lots of updates for deprecated broken stuff, and we have a good
version number to go with it ;)
See the corresponding Rainbows! release for more details:
http://bogomips.org/rainbows-public/m/20140512074058.GB29516@dcvr.yhbt.net
One notable new feature is the addition of the
--no-default-middleware option which I forgot about and should've
released last year when Rainbows! got it :x
Eric Wong (6):
Rakefile: s/freshmeat.net/freecode.com/
Rakefile: kill raa_update task
rubyforge death updates
update license to GPLv2+
warn about premature grandparent death on daemonization
update for Rainbows! compatibility
Lin Jen-Shin (1):
Add -N or --no-default-middleware option.
|
|
Recent versions of Rainbows! and unicorn broke compatibility
during shutdown.
|
|
This may cause failures if some process nukes the grandparent
too soon.
|
|
In case I'm hit by a bus, the lesser of two evils is to have the FSF
potentially screw us with a bad GPLv4 than to be stuck with an
insufficient GPLv3.
|
|
RubyForge is going away tomorrow, update docs + mailing list
to point to the new instances.
|
|
RAA is dead
|
|
This would prevent Unicorn (Zbatery) from adding default middleware,
as if RACK_ENV were always none. (not development nor deployment)
This is implemented in Unicorn, so we only need to update
the option parser here.
Discussion thread on Unicorn mailing list:
http://rubyforge.org/pipermail/mongrel-unicorn/2013-January/001675.html
|
|
I liked Freshmeat more :P
|
|
There are two bugfixes in this release. Rack applications that
use fork() internally should now behave as-expected when
receiving SIGCHLD. The pid file is also unlinked during a
graceful shutdown.
|
|
Applications that fork() will trigger SIGCHLD. As unicorn is
based on the master+worker model, its master process handles
SIGCHLD when workers die. However, Zbatery is single-process
and has no workers, it does not need a custom SIGCHLD handler.
|
|
We don't have the same shutdown sequence as unicorn, there is no
need to leave pid files hanging around during upgrades. Of
course we can't guarantee this (or any) behavior for
non-graceful shutdowns...
|
|
This release fixes a potential reentrancy deadlock when
using the default logger from the Ruby standard library.
|
|
If any combination of signals are sent to Zbatery in a short
period of time, the Mutex used by the default Logger
implementation may deadlock since Mutex synchronization is not
reentrant-safe.
By spawning a thread, we can take advantage of the thread-safety
and avoid the reentrancy-safety issue of acquiring a mutex
inside a signal handler.
Users of alternative logger implementations (or monkey-patched
ones) are possibly not affected. Users of the logger_mp_safe.rb
monkey-patch distributed[1] with unicorn are not affected.
[1] http://unicorn.bogomips.org/examples/logger_mp_safe.rb
|
|
Logging of errors is more consistent in this release.
See the unicorn 4.1.0 release notes for more details:
http://bogomips.org/unicorn.git/tag/?id=v4.1.0
|
|
|
|
|
|
...via Rainbows! 4.3.0.
|
|
We have no public API
|
|
We want email (but not the HTML kind :P)
|
|
This gets most of the improvements Rainbows! 4.0.0 got:
* client_max_header_size directive is added to limit per-client
memory usage in headers.
* An experimental StreamResponseEpoll concurrency option
* minor bugfixes, minor stack depth reduction
Since Zbatery doesn't fork workers, the ability of Unicorn 4.x
to scale to a large amount of worker processes doesn't matter
to us.
|
|
It's no longer needed.
|
|
It's unnecessary making the stack deeper. Stop it.
|
|
There are some internal changes in Unicorn and Rainbows! 4.x
|
|
This fixes locale issues with grep and adds check-warnings.
|
|
This release fixes dependencies on Rainbows! and gets all
the improvements Rainbows! 3.4.0 got:
* Kgio.autopush support for multi-threaded configurations
* Immediate disconnect of idle clients on SIGQUIT for
concurrency models where idle clients are cheap to maintain.
|
|
Like Rainbows! 3.3.0, we've added the GPLv3 to our license
(in addition to GPLv2 and Ruby terms). See Rainbows! 3.3.0
release notes and news for more infor on changes:
http://rainbows.rubyforge.org/NEWS.html
|
|
GPLv2 and Ruby-specific terms remain intact, but this means
we can be combined and redistributed with GPLv3-only software
(once Unicorn has GPLv3 added to its license).
|
|
copy-and-paste error from Rainbows!
|
|
Ruby 1.9.3dev switched to BSD but we remain under the same terms
as the old Ruby 1.8 license. Mongrel2 exists now and also uses
the BSD, so don't confuse people with that, either.
|
|
Small bug fixes that have been sitting around, not much but
it's already been one month since our last release.
* Unicorn dependency updated to 3.4.0, so we get IPv6 support
and Kgio.autopush support for ":tcp_nopush => true" users.
* Optional :pool_size argument is fixed for NeverBlock and
CoolioThreadPool users.
* Mostly minor internal code cleanups
* Sunshowers support removed, it was out-of-date and
unmaintained. Cramp remains supported for now.
* X-Rainbows-* response headers support removed, nobody used it.
There are severalnew features in this release not documented
here. Consider any new features not mentioned in these release
notes to be subject to removal/renaming in future releases.
|
|
Minor updates, really.
|
|
bogomips.org went on a URL diet!
|
|
|
|
About to become Rainbows 3.1.0 soon
|
|
The ugly "Rainbows::G" constant is no longer.
|
|
|
|
|
|
|
|
This release syncs up with the latest from Rainbows! 2.0.x
and Unicorn 3.0.x. See Rainbows! and Unicorn release notes
and changelogs for relevant details.
|
|
This release syncs up with the latest from Rainbows! 1.0.x
and Unicorn 2.0.x
|
|
There are some internal API changes here.
|
|
Small fixes from both that are worth having to ease support.
|
|
Eric Wong (3):
update local.mk.sample for 0.3.0
Fix documentation generation
bump Rainbows! (and Unicorn) dependencies
|
|
Unicorn 1.1.0 had constant resolution problems
with TeeInput
|
|
.document needed to be updated for RDoc 2.5.x
|
|
|
|
Rainbows! v0.95.0 is more awesome than v0.94.0, so we've updated
ourselves to use it and be more awesome as well!
|