From: Joshua Peek <josh@joshpeek.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: ENV["RACK_ENV"] is not set on startup [rack/rack GH-11]
Date: Wed, 31 Mar 2010 15:40:16 -0700 (PDT) [thread overview]
Message-ID: <e41c8cb0-ea30-4b03-b047-fe38f3cf7aa0@r27g2000yqn.googlegroups.com> (raw)
In-Reply-To: <87hbnwr4pu.fsf@gmail.com>
On Mar 31, 8:38 am, Christian Neukirchen <chneukirc...@gmail.com>
wrote:
> > Subject: [GitHub] ENV["RACK_ENV"] is not set on startup [rack/rack GH-11]
>
> > ENV["RACK_ENV"] is not set by rackup on startup, meanwhile at least
> > Passenger, Thin and Unicorn pass this to apps. Besides that Sinatra
> > and Merb use it to set their environment. You can see the discussion
> > about that in the Unicorn list:
> > http://www.mail-archive.com/mongrel-unic...@rubyforge.org/msg00123.html
> > The patch to fix it here:
> >http://github.com/tundraghost/rack/commit/90e9dfedf454a1491d97ab1d145...
+1 I changed Rails to prefer RACK_ENV over RAILS_ENV a while back.
Can we put this convention in "The SPEC"?
next prev parent reply other threads:[~2010-03-31 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 13:38 [GitHub] ENV["RACK_ENV"] is not set on startup [rack/rack GH-11] Christian Neukirchen
2010-03-31 13:58 ` Nicolás Sanguinetti
2010-03-31 14:12 ` James Tucker
2010-03-31 22:40 ` Joshua Peek [this message]
2010-04-01 7:16 ` Eric Wong
2010-04-01 8:21 ` Matt Todd
2010-04-01 8:49 ` James Tucker
2010-04-01 21:13 ` Eric Wong
2010-04-02 4:03 ` Matt Todd
2010-04-08 8:46 ` James Tucker
2010-04-08 11:23 ` Matt Todd
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e41c8cb0-ea30-4b03-b047-fe38f3cf7aa0@r27g2000yqn.googlegroups.com \
--to=rack-devel@googlegroups.com \
/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.
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).