Re: ENV["RACK_ENV"] is not set on startup [rack/rack GH-11]

[Eric Wong <normalperson@yhbt.net>]

James Tucker wrote:
> The possible disparity here is that we use "deployment" and "none"
> traditionally (with Yehudas Rack::Server deprecating "none" to be
> implicit instead). I think the best option is to map "production" to
> "deployment" for the time being, and maybe look at deprecating
> "deployment" in say, a year, if at all (don't really see why it needs
> to be removed tbh, other than neatness).

Joshua Peek <josh@joshpeek.com> wrote:
> +1 I changed Rails to prefer RACK_ENV over RAILS_ENV a while back.

What happens when Rails sees "none" or an empty value?

I've always preferred to start Rack with "none"/empty since I didn't
like the Rack::CommonLogger defaulting to $stderr which I believe should
be reserved for more critical messages.  I also prefer Clogger instead
of CommonLogger for access logs.

With RACK_ENV != RAILS_ENV, it was easy to deploy a Rails app without
the RACK_ENV=deployment defaults (which I don't want) conflicting
with the RAILS_ENV=production defaults (which I do want).   I guess
those apps will have to be reconfigured to use RAILS_ENV=none (or
RAILS_ENV=something_rack_will_never_understand :)

-- 
Eric Wong


-- 
To unsubscribe, reply using "remove me" as the subject.