about summary refs log tree commit homepage
path: root/unicorn.gemspec
DateCommit message (Collapse)
2017-03-23gemspec: remove olddoc from build dependency
It's a little less DRY, and there'll be no NEWS file generated, but it's one less thing to install, so perhaps that's worth it. The website at https://bogomips.org/unicorn/ will continue to use olddoc, of course,
2016-01-27rack is optional at runtime, required for dev
We do not want to pull in a newer or older version of rack depending on an the application running under it requires. Furthermore, it has always been possible to use unicorn without any middleware at all. Without rack, we'll be missing descriptive status text in the first response line, but any valid HTTP/1.x parser should be able to handle it properly. ref: http://bogomips.org/unicorn-public/20160121201255.GA6186@dcvr.yhbt.net/t/#u Thanks-to: Adam Duke <adam.v.duke@gmail.com> Thanks-to: Aaron Patterson <tenderlove@ruby-lang.org>
2016-01-09doc: bump olddoc to ~> 1.2 for extra NNTP URL
Additional advertising for the gmane NNTP server makes sense from a robustness standpoint: nntp://news.gmane.org/gmane.comp.lang.ruby.unicorn.general Not advertising other HTTP-based URLs just yet. They could contain images/frames/JS/CSS and add unnecessary clutter to the footer. NNTP puts the client in control of UI.
2015-11-01gemspec: relax Ruby version requirement for old RubyGems
Older RubyGems (1.8.23.2 at least) does not seem to support multiple version requirements for the Ruby version; so drop the lower 1.9.3 requirement for now.
2015-08-22gemspec: limit to 1.9.3 and 2.x
It does not look like we'll be compatible with Ruby 3.0 with the plan for immutable string literals. However, keep in mind 3.0 is still many years away and decisions can change, so it would be premature to stop assuming frozen string literals this year. ref: https://bugs.ruby-lang.org/issues/11473
2015-01-17gemspec: fixup olddoc migration
rdoc_options is no longer necesary with olddoc as olddoc can infer document titles and only generates cgit-compatible URLs to source code.
2015-01-10switch 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.
2014-08-17remove RubyForge and Freecode references
Both sites are gone.
2014-08-17unicorn.gemspec: depend on test-unit 3.0
test-unit 3 and minitest 5 will have equal support status as a bundled gems when Ruby 2.2.0 is released in December 2014. These bundled gems will appear in the user-oriented tarball installations, but do not get installed by "make install" when installing Ruby from SVN or git. test-unit appears to be actively maintained and good at keeping backwards compatibility even on a major version change, so this means no code changes on our end. I am not convinced switching to minitest is worth the effort. Cc: Ken Dreyer <ktdreyer@ktdreyer.com>
2014-08-17dev: remove isolate dependency
It seems unnecessary with current versions of RubyGems supporting development dependencies.
2014-05-06swap out most of the rubyforge.org links
Update the old mailing list info with our new public-inbox info. The old mongrel.rubyforge.org links have been dead for years, oh well. There's only a few days left of RubyForge left...
2013-10-26license: allow all future versions of the GNU GPL
There is currently no GPLv4, so this change has no effect at the moment. In case the GPLv4 arrives and I am not alive to approve/review it, the lesser of evils is have give blanket approval of all future GPL versions (as published by the FSF). The worse evil is to be stuck with a license which cannot guarantee the Free-ness of this project in the future. This unfortunately means the FSF can theoretically come out with license terms I do not agree with, but the GPLv2 and GPLv3 will always be an option to all users.
2012-12-04gemspec: enable licenses metadata attribute
This enables compatibility with metadata scanners such as LicenseFinder[1]. The previously commented-out accessor was commented out in September 2009 when ancient RubyGems were more prevalent. By now (December 2012), those ancient versions of RubyGems are unlikely to be around. [1] https://github.com/pivotal/LicenseFinder [ew: rewritten commit message] Signed-off-by: Eric Wong <normalperson@yhbt.net>
2011-12-05bump dependencies
We should always be testing with the newest available versions to watch for incompatibilities, even if we don't /require/ the latest ones to run.
2011-08-19gemspec: bump wrongdoc dependency for dev
Hopefully it points people towards the mailing list
2011-06-22gemspec: fix raindrops dependency
Oops, I suck at Ruby :x
2011-06-16replace fchmod()-based heartbeat with raindrops
This means we no longer waste an extra file descriptor per worker process in the master. Now there's no need to set a higher file descriptor limit for systems running >= 1024 workers.
2011-06-13gemspec: bump kgio dependency to ~> 2.4
kgio 2.4.1 portability should be better than 2.3, so less user confusion and push them towards 2.4
2011-05-23gemspec: use latest Isolate (3.1)
It's required for RubyGems 1.8.x
2011-03-08gemspec: update kgio dependency to 2.3.2
People reinstalling would've pulled it in anyways, but 2.3.2 is the latest and has no known issues.
2011-03-08gemspec: no need for require_paths
2011-02-04bump dependency on kgio
This is needed for IPv6 support, and 2.2.0 is nicer all around for Rainbows! users. Updates wrongdoc while we're at it, too.
2011-01-05unicorn 3.3.0 - minor optimizations v3.3.0
Certain applications that already serve hundreds/thousands of requests a second should experience performance improvements due to Time.now.httpdate usage being removed and reimplemented in C. There are also minor internal changes and cleanups for Rainbows!
2010-12-26gemspec: fix gemspec build
Oops
2010-12-26bump kgio dependency to ~> 2.1
The kgio 2.x series will maintain API compatibility until 3.x, so it's safe to use any 2.x release.
2010-12-25doc: use wrongdoc for documentation
wrongdoc factors out a bunch of common code from this project into its own and removes JavaScript from RDoc to boot.
2010-11-19update to kgio 2.x series
The Kgio 2.x API is less brain-damaged than the 1.3.x series was, and should solve API-compatibility problems with dalli 0.11.1.
2010-10-27doc: stop using deprecated rdoc CLI options
-N and -a switches no longer exist in rdoc 2.5
2010-10-27gemspec: depend on Isolate 3.0.0 for dev
No reason to not use the latest and greatest!
2010-10-08bump kgio dependency
kgio 1.3.1 fixes some cases for zero-length reads.
2010-10-08bump kgio dependency to 1.3.0
There was a backwards-incompatible API change, but that didn't even affect us.
2010-10-07gemspec: bump kgio version
kgio 1.2.1 works around a bug for some *BSDs, some of which are popular platforms for developers.
2010-10-06gemspec: depend on newer isolate
We use the latest and greatest whenever possible.
2010-10-05upgrade to kgio 1.2.0
This provides the kgio_read! method which is like readpartial, only significantly cheaper when a client disconnects on us.
2010-10-05start using kgio, the kinder, gentler I/O library
This should hopefully make the non-blocking accept() situation more tolerable under Ruby 1.9.2.
2010-06-11doc: cleanup rdoc escaping in title, hopefully
2010-06-10README: more aggressively kill unnecessary links
... And make the gemspec do minor un-RDoc-ing
2010-06-03gemspec: add development dependency on isolate
2009-11-21doc: "RubyGems" is the correct capitalization
So says the project website and documentation
2009-11-15Rakefile: add raa_update task
2009-10-16KNOWN_ISSUES: document Rack gem issue w/Rails 2.3.2
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.
2009-10-09README: emphasize the "fast clients"-only part
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.
2009-10-05doc: make it clear contributors retain copyrights
We hope to never require copyright assignment here...
2009-09-28gemspec: clarify commented-out licenses section
It may have caused confusion that the licenses we're under were incompatible with older Rubygems which is not the case.
2009-09-27gemspec: remove tests that fork from test_files
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.
2009-09-27gemspec: fix test_files regexp match
Not sure if anybody runs tests with Rubygems directly (instead of unpacking the source tree, but it's there)
2009-09-24gemspec: compatibility with older Rubygems
"licenses=" is not in older Rubygems and some organizations are still stuck on those...
2009-09-18README/gemspec: a better description, hopefully
2009-09-17Remove Echoe and roll our own packaging/release...
* 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.