about summary refs log tree commit homepage
diff options
context:
space:
mode:
-rw-r--r--LICENSE2
-rw-r--r--README35
-rw-r--r--Rakefile2
-rw-r--r--SIGNALS6
-rw-r--r--lib/rainbows/const.rb2
-rw-r--r--rainbows.gemspec2
6 files changed, 33 insertions, 16 deletions
diff --git a/LICENSE b/LICENSE
index cef611a..c571b10 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,4 +1,4 @@
-Rainbows is copyrighted free software by Eric Wong
+Rainbows! is copyrighted free software by Eric Wong
 (mailto:normalperson@yhbt.net) and contributors. You can redistribute it
 and/or modify it under either the terms of the
 {GPL2}[http://www.gnu.org/licenses/gpl-2.0.txt] (see link:COPYING) or
diff --git a/README b/README
index 0c5f8c6..def4dce 100644
--- a/README
+++ b/README
@@ -1,6 +1,6 @@
-= Rainbows: Unicorn for Comet and slow clients
+= Rainbows! Unicorn for Comet and slow clients
 
-Rainbows is a HTTP server for {Rack}[http://rack.rubyforge.org/]
+Rainbows! is a HTTP server for {Rack}[http://rack.rubyforge.org/]
 applications.  It is based on {Unicorn}[http://unicorn.bogomips.org/],
 but designed to handle applications that expect long request/response
 times and/or slow clients.  It is designed for Comet applications and
@@ -24,14 +24,14 @@ and easier to debug.
 
 == License
 
-Rainbows is copyright 2009 Eric Wong and contributors.  It is based on
+Rainbows! is copyright 2009 Eric Wong and contributors.  It is based on
 Mongrel and Unicorn and carries the same license.
 
 Mongrel is copyright 2007 Zed A. Shaw and contributors. It is licensed
 under the Ruby license and the GPL2. See the included LICENSE file for
 details.
 
-Rainbows is 100% Free Software.
+Rainbows! is 100% Free Software.
 
 == Usage
 
@@ -41,21 +41,38 @@ In APP_ROOT (where config.ru is located), run:
 
   rainbows
 
-Rainbows will bind to all interfaces on TCP port 8080 by default.
+Rainbows! will bind to all interfaces on TCP port 8080 by default.
 
 === Configuration File(s)
 
-Rainbows will look for the config.ru file used by rackup in APP_ROOT.
+Rainbows! will look for the config.ru file used by rackup in APP_ROOT.
 
-For deployments, it can use a config file for Rainbows-specific options
-specified by the +--config-file/-c+ command-line switch.  See
-Rainbows::Configurator for the syntax of the Rainbows-specific options.
+For deployments, it can use a config file for Unicorn and
+Rainbows!-specific options specified by the +--config-file/-c+
+command-line switch.  Rainbows! accepts all options found in
+{Unicorn::Configurator}[http://unicorn.bogomips.org/Unicorn/Configurator.html]
+as well as the "Rainbows!" block, so you can have the following in your
+config file:
+
+    Rainbows! do
+      use :Revactor
+      worker_connections 128
+    end
 
 == Development
 
 * git: git://git.bogomips.org/rainbows.git
 * cgit: http://git.bogomips.org/cgit/rainbows.git
 
+Inline patches (from "git format-patch") to the mailing list are
+preferred because they allow code review and comments in the reply to
+the patch.
+
+We will adhere to mostly the same conventions for patch submissions as
+git itself.  See the Documentation/SubmittingPatches document
+distributed with git on on patch submission guidelines to follow.  Just
+don't email the git mailing list or maintainer with Rainbows! patches.
+
 == Disclaimer
 
 There is NO WARRANTY whatsoever if anything goes wrong, but let us know
diff --git a/Rakefile b/Rakefile
index f638459..d2025ce 100644
--- a/Rakefile
+++ b/Rakefile
@@ -32,7 +32,7 @@ task :news_atom do
   puts(Nokogiri::XML::Builder.new do
     feed :xmlns => "http://www.w3.org/2005/Atom" do
       id! "http://rainbows.rubyforge.org/NEWS.atom.xml"
-      title "Rainbows news"
+      title "Rainbows! news"
       subtitle "Unicorn for Comet and slow clients"
       link! :rel => 'alternate', :type => 'text/html',
             :href => 'http://rainbows.rubyforge.org/NEWS.html'
diff --git a/SIGNALS b/SIGNALS
index fe68fa9..84f6bb4 100644
--- a/SIGNALS
+++ b/SIGNALS
@@ -1,8 +1,8 @@
 == Signal handling
 
-In general, signals need only be sent to the master process.  However, the
-signals Rainbows uses internally to communicate with the worker processes are
-documented here as well.
+In general, signals need only be sent to the master process.  However,
+the signals Rainbows! uses internally to communicate with the worker
+processes are documented here as well.
 
 === Master Process
 
diff --git a/lib/rainbows/const.rb b/lib/rainbows/const.rb
index 76b5d8f..ca6e2d4 100644
--- a/lib/rainbows/const.rb
+++ b/lib/rainbows/const.rb
@@ -13,7 +13,7 @@ module Rainbows
       # with Revactor or Rev, so we're considered multithread-ed even
       # when we're not technically...
       "rack.multithread" => true,
-      "SERVER_SOFTWARE" => "Rainbows #{RAINBOWS_VERSION}",
+      "SERVER_SOFTWARE" => "Rainbows! #{RAINBOWS_VERSION}",
     })
 
     CONN_CLOSE = "Connection: close\r\n"
diff --git a/rainbows.gemspec b/rainbows.gemspec
index b542553..61f6fe2 100644
--- a/rainbows.gemspec
+++ b/rainbows.gemspec
@@ -34,7 +34,7 @@ Gem::Specification.new do |s|
   s.files = manifest
   s.homepage = %q{http://rainbows.rubyforge.org/}
   s.summary = %q{Unicorn for Comet and slow clients}
-  s.rdoc_options = [ "-Na", "-t", "Rainbows #{s.summary}" ]
+  s.rdoc_options = [ "-Na", "-t", "Rainbows! #{s.summary}" ]
   s.require_paths = %w(lib)
   s.rubyforge_project = %q{rainbows}