Skip to content

Commit

Permalink
manpage: update middleware-related documentation
Browse files Browse the repository at this point in the history
-N/--no-default-middleware needs a corresponding manpage entry.

Additionally, the Rack::Chunked/ContentLength middleware comment
is out-of-date as of unicorn v4.1.0
  • Loading branch information
Eric Wong committed Jan 29, 2013
1 parent db919d1 commit 64765b9
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions Documentation/unicorn.1.txt
Original file line number Diff line number Diff line change
Expand Up @@ -61,6 +61,10 @@ with rackup(1) but strongly discouraged.
For production deployments, specifying the "listen" directive in
CONFIG_FILE is recommended as it allows fine-tuning of socket
options.
-N, \--no-default-middleware
: Disables loading middleware implied by RACK_ENV. This bypasses the
configuration documented in the RACK ENVIRONMENT section, but still
allows RACK_ENV to be used for application/framework-specific purposes.

# RACKUP COMPATIBILITY OPTIONS
-o, \--host HOST
Expand Down Expand Up @@ -144,10 +148,10 @@ As of Unicorn 0.94.0, RACK_ENV is exported as a process-wide environment
variable as well. While not current a part of the Rack specification as
of Rack 1.0.1, this has become a de facto standard in the Rack world.

Note that the Rack::ContentLength and Rack::Chunked middlewares
are never loaded by default. If needed, they should be
individually specified in the RACKUP_FILE, some frameworks do
not require them.
Note the Rack::ContentLength and Rack::Chunked middlewares are also
loaded by "deployment" and "development", but no other values of
RACK_ENV. If needed, they must be individually specified in the
RACKUP_FILE, some frameworks do not require them.

# ENVIRONMENT VARIABLES

Expand Down

0 comments on commit 64765b9

Please sign in to comment.