about summary refs log tree commit homepage
path: root/README
DateCommit message (Collapse)
2020-01-20doc: s/bogomips.org/yhbt.net/g
bogomips.org is due to expire, soon, and I'm not willing to pay extortionist fees to Ethos Capital/PIR/ICANN to keep a .org. So it's at yhbt.net, for now, but it will change again to whatever's affordable... Identity is overrated. Tor users can use .onions and kick ICANN to the curb: torsocks w3m http://unicorn.ou63pmih66umazou.onion/ torsocks git clone http://ou63pmih66umazou.onion/unicorn.git/ torsocks w3m http://ou63pmih66umazou.onion/unicorn-public/ While we're at it, `s/news.gmane.org/news.gmane.io/g', too. (but I suspect that'll need to be resynched since our mail "List-Id:" header is changing).
2018-12-19README: minor updates and additional disclaimer
Nowadays, I mainly rely on systemd (and not USR2) for zero-downtime upgrades. Also, CoW-friendliness is standard in mainline Ruby since 2.0. There also needs to be a disclaimer to point out the unfortunate side-effect of robustness for hosting buggy apps.
2018-10-18doc: update more URLs to use HTTPS and avoid redirects
Latency from redirects is painful, and HTTPS can protect privacy in some cases.
2016-10-25relocate website to https://bogomips.org/unicorn/
HTTPS helps some with reader privacy and Let's Encrypt seems to be working well enough the past few months. This change will allow us to reduce subjectAltName bloat in our TLS certificate over time. It will also promote domain name agility to support mirrors or migrations to other domains (including a Tor hidden service mirror). http://bogomips.org/unicorn/ will remain available for people on legacy systems without usable TLS. There is no plan for automatic redirecting from HTTP to HTTPS at this time.
2016-03-31doc: further trimming to reduce noise
It's not worth mentioning pre-Rack versions of Rails anymore, and there are a few async Rack applications reliant on EventMachine which we do not use. Some uses of chunked request decoding are not well-handled with nginx in front, anyways; so avoid mentioning them. Additionally, avoid introducing new terms into the lexicon and just refer to "mailing list" as a generic term.
2016-01-07various documentation updates
* add nntp_url to the olddoc website footer * update legacy support status for 4.x (not 4.8.x) * update copyright range to 2016 * note all of our development tools are Free Software, too * remove cgit mention; it may not always be cgit (but URLs should remain compatible). * discourage downloading snapshot tarballs; "git clone" + periodic "git fetch" is more efficient * remove most mentions of unicorn_rails as that was meant for ancient Rails 1.x/2.x users * update path reference to Ruby 2.3.0 * fix nginx upstream module link to avoid redirect * shorten Message-ID example to avoid redirects and inadvertant linkage
2015-10-05doc: update mail archive info
public-inbox supports read-only NNTP access nowadays to make it easier to follow archives. It is read-only to encourage Cc:-ing all participants (which avoids reliance on the few-points-of-failure behavior of NNTP). Unlike email, NNTP also lacks good anti-spam filtering. Additionally, the gmane group also got redirected to the bogomips.org address at some point since RubyForge died. While we're at it, link to my post about enabling the submission port (587). It's been a year and nothing bad has happened, yet. Finally, remove most of the documentation for ssoma since it's unlikely anybody will use it given the existence of NNTP access. It did little besides clutter the page. However, git:// (used by ssoma) remains strictly more efficient than NNTP. Vebavpnyyl, gur AAGC freire sbe choyvp-vaobk pna unaqyr gubhfnaqf bs fybj pyvragf. Fbzrguvat havpbea jvyy arire or noyr gb qb :C
2015-07-15doc: remove references to old servers
They'll continue to be maintained, but we're no longer advertising them. Also, favor lowercase "unicorn" while we're at it since that matches the executable and gem name to avoid unnecessary escaping for RDoc.
2015-06-26doc: update some invalid URLs
Most of these were found by the `linkchecker' package in Debian.
2015-02-06doc: update support status for Ruby versions
unicorn 5 will not support Ruby 1.8 anymore. Drop mentions of Rubinius, too, it's too difficult to support due to the proprietary and registration-required nature of its bug tracker. The smaller memory footprint and CoW-friendly memory allocator in mainline Ruby is a better fit for unicorn, anyways. Since Ruby 1.9+ bundles RubyGems and gem startup is faster nowadays, we'll just depend on that instead of not loading RubyGems. Drop the local.mk.sample file, too, since it's way out-of-date and probably isn't useful (I have not used it in a while).
2015-01-10README: clarify/reduce references to unicorn_rails
unicorn_rails is an ancient compatibility wrapper for ancient versions of Rails which did not use Rack. Those applications have likely moved on, so stop promoting unicorn_rails.
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-04README: clarify license and copyright
Since Ruby 1.9.3, (Matz) Ruby is licensed under a 2-clause BSDL. Thus we need to clarify we inherited the license terms from Ruby 1.8 to prevent misunderstanding. (The Ruby license change cannot alter the license of other projects automatically) Since we added the GPLv3 as an additional license in 2011, the license terms of unicorn no longer matches Mongrel 1.1.5. This is NOT a change to the unicorn license at all, just a wording clarification.
2011-08-29add GPLv3 option to the license
Existing license terms (Ruby-specific) and GPLv2 remain in place, but GPLv3 is preferred as it helps with distribution of AGPLv3 code and is explicitly compatible with Apache License (v2.0). Many more reasons are documented by the FSF: https://www.gnu.org/licenses/quick-guide-gplv3.html http://gplv3.fsf.org/rms-why.html ref: http://thread.gmane.org/gmane.comp.lang.ruby.unicorn.general/933
2011-03-22README: s/Gemcutter/RubyGems.org/
Gemcutter is the old name
2011-02-16README: clarify the versions of "Ruby license"
Ruby 1.9.3dev is now using the 2-clause BSD License, not the GPLv2. Do not mislead people into thinking we will switch to any BSD License, we won't.
2011-01-21git.bogomips.org => bogomips.org
bogomips.org is slimming down and losing URL weight :)
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-05-04README: avoid needless links to /Unicorn.html module
It makes the HTML page too big and busy.
2009-12-07doc: add ISSUES document
2009-11-21README: deployments are not as rare as previously thought
Either people are actually using it or somebody is running a script to download gems off gemcutter in a loop... I suspect the former...
2009-11-21README: add a note about the HACKING page
2009-11-21README: remove http:// git repo links
Nobody really uses or cares for them anyways
2009-11-21doc: "RubyGems" is the correct capitalization
So says the project website and documentation
2009-11-21README: "an HTTP" server seems to be the correct form
Grammar na^H^Hexperts please correct us again if we're wrong.
2009-11-21README: Gemcutter is our (and everyone elses) gem host now
2009-10-12README: alter reply conventions for the mailing list
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.
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-09README: remove the "non-existent" part
Still pretty rare, though.
2009-10-09README: remove unnecessary and extraneous dash
2009-10-05doc: make it clear contributors retain copyrights
We hope to never require copyright assignment here...
2009-10-01README: remove reference to different versions
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.
2009-09-24Split out KNOWN_ISSUES document
This deserves to be a separate document and easier to find/edit.
2009-09-18README/gemspec: a better description, hopefully
2009-09-18unicorn 0.92.0 v0.92.0
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.
2009-09-18doc: latest news is available through finger
We're expanding our target audience to folks that do not use HTTP (yet).
2009-09-15Update documentation for Rubinius support status
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.
2009-09-04README: update with current version
2009-08-17Documentation updates
* 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.
2009-08-16unicorn 0.90.0 v0.90.0
2009-08-15README: everybody loves Ruby DSLs
2009-08-10Documentation updates
2009-08-06README: latest stable version is 0.8.4
2009-07-19README: update version numbers for website
2009-07-14README: update about development/stable versions
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.
2009-07-14README: add Gmane newsgroup info
2009-06-29README: another note about older Sinatra
Older Sinatra would blindly try to run Mongrel or Thin at_exit. This causes strange behavior to happen when Unicorn workers are exited.
2009-06-06README: update with mailing list info