From: Eric Wong <normalperson@yhbt.net>
To: mongrel-unicorn@rubyforge.org
Subject: [PATCH] manpage: update middleware-related documentation
Date: Tue, 29 Jan 2013 21:23:10 +0000 [thread overview]
Message-ID: <20130129212310.GA16030@dcvr.yhbt.net> (raw)
In-Reply-To: <20130129211015.GA8686@dcvr.yhbt.net>
-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
---
Also just pushed this to master of git://bogomips.org/unicorn
commit 64765b95df06256d39daefdeebde97c874770131
Documentation/unicorn.1.txt | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/Documentation/unicorn.1.txt b/Documentation/unicorn.1.txt
index c20a570..a42dfff 100644
--- a/Documentation/unicorn.1.txt
+++ b/Documentation/unicorn.1.txt
@@ -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
@@ -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
--
1.8.1.2.422.g08c0e7f
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2013-01-29 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 21:10 [ANN] unicorn 4.6.0pre1 - hijacking support! Eric Wong
2013-01-29 21:23 ` Eric Wong [this message]
2013-02-04 13:40 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130129212310.GA16030@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=mongrel-unicorn@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).