0
@@ -64,7 +64,6 @@ And you can run migrations with:
0
   # or with a version number
0
   rake schema:migrate version=1
0
 
0
-
0
 === Mappings
0
 
0
 Mappings are the Waves equivalent to routes.  An individual mapping consists of a request-matching construct and an arbitrary block.  When a request matches a mapping, Waves runs that block.  In the simplest case, you do all the response work in the block, a la {Sinatra}[http://sinatrarb.com/Home].  The standard Waves application also offers an MVC infrastructure, with a silent R for Resource.
0
@@ -155,5 +154,18 @@ The result is that you only need to define models, views, etc. <i>when the defau
0
     templates/         # Views expect templates to live here.
0
     views/             # (auto_load || auto_create)
0
 
0
+=== Web Server
0
+
0
+You can run on any {Rack-supported Web server}[], including Thin and Mongrel. Just edit your configuration file, like you did for your database settings(<tt>configurations/development.rb) and change the <tt>handler</tt> parameter. The default is Mongrel. For example, to switch to Thin:
0
+
0
+  handler ::Rack::Handler::Thin, :Host => host, :Port => port
0
+
0
+In addition, you can also configure your Rack application the same way. Just edit the <tt>application</tt> parameter:
0
+
0
+  application do
0
+    use ::Rack::ShowExceptions
0
+    use Rack::CommonLogger
0
+    run ::Waves::Dispatchers::Default.new
0
+  end
0
 
0