rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Refactor tests that switch RAILS_ENV and RACK_ENV	Carlos Antonio da Silva	2012-12-06	1	-14/+10
\| \| \| \| \| \| \| \| \| \| \| \|	This cleanup aims to fix a build failure: https://travis-ci.org/rails/rails/jobs/3515951/#L482 Since travis always have both ENV vars set to "test", a test is failing where it's expected to output the default env "development", but "test" is the result due to RACK_ENV being set when we expect it to not be. By cleaning this duplication we ensure that changing any of these env variables will pick the right expected value.
*	Add ENV['RACK_ENV'] support to rake runner/console/server.	kennyj	2012-12-06	1	-0/+20
\|
*	Remove support for rails server RAILS_ENV=env-name	Sam Oliver	2012-05-30	1	-2/+2
\|
*	fix rails server support of RAILS_ENV variable	schneems	2012-03-20	1	-0/+26
	When launching rails server from the command line with a rails environment specified such as `rails server RAILS_ENV=production` an error would occur since rails will try to use `RAILS_ENV=production` as it's server. When launching rails with a specified server such as thin `rails server thin RAILS_ENV=production` no error will be thrown, but rails will not start up in the specified environment. This fixes both of those cases