chneukirchen / rack

a modular Ruby webserver interface

This URL has Read+Write access

rack / README
100644 155 lines (108 sloc) 5.051 kb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
= Rack, a modular Ruby webserver interface
 
Rack provides minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
 
The exact details of this are described in the Rack specification,
which all Rack applications should conform to.
 
== Supported web servers
 
The included *handlers* connect all kinds of web servers to Rack:
* Mongrel
* WEBrick
* FCGI
* CGI
 
Any valid Rack app will run the same on all these handlers, without
changing anything.
 
== Supported web frameworks
 
The included *adapters* connect Rack with existing Ruby web frameworks:
* Camping
* Rails (alpha)
* more to come soon, ...
 
These frameworks include Rack adapters in their distributions:
* Ramaze
* Maveric
* Racktools::SimpleApplication
 
== Available middleware
 
Between the server and the framework, Rack can be customized to your
applications needs using middleware, for example:
* Rack::URLMap, to route to multiple applications inside the same process.
* Rack::CommonLogger, for creating Apache-style logfiles.
* Rack::ShowException, for catching unhandled exceptions and
  presenting them in a nice and helpful way with clickable backtrace.
* Rack::File, for serving static files.
* ...
 
All these components use the same interface, which is described in
detail in the Rack specification. You can choose to use them exactly
in the way you want.
 
== Convenience
 
If you want to develop outside of existing frameworks, implement your
own ones, or develop middleware, Rack provides many helpers to create
Rack applications quickly and without doing the same web stuff all
over:
* Rack::Request, which also provides query string parsing and
  multipart handling.
* Rack::Response, for convenient generation of HTTP replies and
  cookie handling.
* Rack::MockRequest and Rack::MockResponse for efficient and quick
  testing of Rack application without real HTTP round-trips.
 
== rackup
 
rackup is a useful tool for running Rack applications, which uses the
Rack::Builder DSL to configure middleware and build up applications
easily.
 
rackup automatically figures out the environment it is run in, and
runs your application as FastCGI, CGI, or standalone with Mongrel or
WEBrick---all from the same configuration.
 
== Quick start
 
Try the lobster!
 
Either with the embedded WEBrick starter:
 
  ruby -Ilib lib/rack/lobster.rb
 
Or with rackup:
 
  bin/rackup -Ilib example/lobster.ru
 
By default, the lobster is found at http://localhost:9292.
 
== Installing with RubyGems
 
A Gem of Rack is available. You can install it with:
 
    gem install rack
 
I also provide a local mirror of the gems (and development snapshots)
at my site:
 
    gem install rack --source http://chneukirchen.org/releases/gems
 
== History
 
* March 3rd, 2007: First public release 0.1.
 
== Contact
 
Please mail bugs, suggestions and patches to
<mailto:chneukirchen@gmail.com>.
 
Darcs repository ("darcs send" is welcome for patches):
http://chneukirchen.org/repos/rack
 
You are also welcome to join the #rack channel on irc.freenode.net.
 
== Thanks to
 
* Michael Fellinger, for the helpful discussion.
* Christoffer Sawicki, for the Rails adapter.
* Armin Ronacher, for the logo and racktools.
* Alexander Kellett for testing the Gem and reviewing the announce.
* Marcus Rückert, for help with configuring and debugging lighttpd.
* The WSGI team for the well-done and documented work they've done and
  Rack builds up on.
 
== Copyright
 
Copyright (C) 2007 Christian Neukirchen <http://purl.org/net/chneukirchen>
 
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
 
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
 
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
 
== Links
 
Rack:: <http://rack.rubyforge.org/>
Rack's Rubyforge project:: <http://rubyforge.org/projects/rack>
 
Camping:: <http://camping.rubyforge.org/>
Ramaze:: <http://ramaze.rubyforge.org/>
Maveric:: <http://maveric.rubyforge.org/>
racktools:: <http://lucumr.pocoo.org/trac/repos/racktools/>
 
Christian Neukirchen:: <http://chneukirchen.org/>