about summary refs log tree commit homepage
DateCommit message (Collapse)
2015-03-01README: reference yahns HEAD master
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.
2015-01-13switch docs + website to olddoc
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).
2014-05-14doc: fix pandoc HTML generation
The --sanitize-html option is gone nowadays.
2014-05-14zbatery 4.2.0 v4.2.0
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.
2014-05-14update for Rainbows! compatibility
Recent versions of Rainbows! and unicorn broke compatibility during shutdown.
2014-05-14warn about premature grandparent death on daemonization
This may cause failures if some process nukes the grandparent too soon.
2014-05-14update license to GPLv2+
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.
2014-05-14rubyforge death updates
RubyForge is going away tomorrow, update docs + mailing list to point to the new instances.
2013-09-30Rakefile: kill raa_update task
RAA is dead
2013-01-29Add -N or --no-default-middleware option.
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
2011-12-07Rakefile: s/freshmeat.net/freecode.com/
I liked Freshmeat more :P
2011-12-05Zbatery 4.1.2 - we don't fork, but our apps may! v4.1.2
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.
2011-12-02use default SIGCHLD handler
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.
2011-11-23zbatery: unlink pid file during graceful shutdown
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...
2011-09-02Zbatery 4.1.1 - small bugfix v4.1.1
This release fixes a potential reentrancy deadlock when using the default logger from the Ruby standard library.
2011-08-31avoid potential Logger deadlocks in signal handling
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
2011-08-20Zbatery 4.1.0 - pull in latest changes from unicorn 4.1.0 v4.1.0
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
2011-08-20t/test_isolate: bump test dependency versions
2011-08-20README: various doc updates
2011-08-20gemspec: depend on unicorn 4.1.0
...via Rainbows! 4.3.0.
2011-08-20cleanup rdoc
We have no public API
2011-08-20bump wrongdoc to 1.6
We want email (but not the HTML kind :P)
2011-06-27Zbatery 4.0.0 - another Rainbows! resync v4.0.0
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.
2011-06-27remove DeadIO class
It's no longer needed.
2011-06-27remove Zbatery.run method
It's unnecessary making the stack deeper. Stop it.
2011-06-27resync with Rainbows! 4.0.0
There are some internal changes in Unicorn and Rainbows! 4.x
2011-05-21pkg.mk: update to the latest version
This fixes locale issues with grep and adds check-warnings.
2011-05-21Zbatery 3.4.0 - another Rainbows! resync v3.4.0
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.
2011-05-16Zbatery 3.3.0 - another Rainbows! resync v3.3.0
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
2011-05-10LICENSE: add GPLv3 terms
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).
2011-02-16GNUmakefile: fix doc build
copy-and-paste error from Rainbows!
2011-02-16README: clarify license terms and versions
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.
2011-02-11Zbatery 3.1.0 - we stole release notes from Rainbows! v3.1.0
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.
2011-02-11bump Rainbows! dependency to 3.1.0
Minor updates, really.
2011-02-11update packaging and URLs
bogomips.org went on a URL diet!
2011-02-11bump up wrongdoc dependency
2011-02-11update for internal API change in rainbows.git
About to become Rainbows 3.1.0 soon
2011-01-11Zbatery 3.0.0 - Rainbows! 3.0.0 resync v3.0.0
The ugly "Rainbows::G" constant is no longer.
2010-12-29Zbatery 0.6.0 - Rainbows! 2.1.x resync v0.6.0
2010-12-29packaging updates (wrongdoc!)
2010-12-29resync with Rainbows! 2.1.0
2010-11-20Zbatery 0.5.0 - Rainbows! 2.0.x sync v0.5.0
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.
2010-10-28Zbatery 0.4.0 - Rainbows! 1.0.x sync v0.4.0
This release syncs up with the latest from Rainbows! 1.0.x and Unicorn 2.0.x
2010-10-28updates for Rainbows! 1.0.0
There are some internal API changes here.
2010-08-28bump dependencies on Unicorn + Rainbows!
Small fixes from both that are worth having to ease support.
2010-07-11Zbatery v0.3.1 - quiet EOF errors from clients v0.3.1
Eric Wong (3): update local.mk.sample for 0.3.0 Fix documentation generation bump Rainbows! (and Unicorn) dependencies
2010-07-11bump Rainbows! (and Unicorn) dependencies
Unicorn 1.1.0 had constant resolution problems with TeeInput
2010-07-10Fix documentation generation
.document needed to be updated for RDoc 2.5.x
2010-07-10update local.mk.sample for 0.3.0
2010-07-10Zbatery v0.3.0 - for newer Rainbows! v0.3.0
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!