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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Set RACK_ENV to nil in the dbconsole test	Rafael Mendonça França	2012-05-30	1	-0/+1
\| \| \| \|	This will fix the travis-ci build
*	Remove support for rails server RAILS_ENV=env-name	Sam Oliver	2012-05-30	1	-2/+2
\|
*	Fix various bugs with console arguments.	Sam Oliver	2012-05-30	2	-39/+71
\| \| \| \|	Allow hyphens in environment names again.
*	More assert_match warnings fixed.	Arun Agrawal	2012-05-30	2	-8/+8
\|
*	Fix `rails db -h` and cosmetic fixes in usage banners	Alexey Vakhov	2012-05-22	1	-0/+18
\| \| \| \| \| \| \|	Ruby tries to use '-h' as short version of '--header' by default https://github.com/ruby/ruby/blob/trunk/lib/optparse.rb#L1372-1381. To force `rails db -h` prints an usage message we should add the `-h` options explicitly.
*	Use relative path to sqlite3 db in `rails db` command	Alexey Vakhov	2012-05-22	1	-6/+11
\| \| \| \| \| \| \| \| \| \|	Rails uses sqlit3 db file with a path relative to the rails root. It allows to execute server not from rails root only. For example you can fire `./spec/dummy/script/rails s` to start dummy application server if you develop some engine gem. Now the `rails db` command uses relative paths also and you can explore your dummy db via `./spec/dummy/script/rails db` command.
*	Fix build	Piotr Sarnacki	2012-05-06	1	-7/+10
\|
*	More faster rails dbconsole	Dmitry Vorotilin	2012-05-06	1	-28/+57
\|
*	Add Rails::DBConsole tests	Alexey Vakhov	2012-05-02	1	-0/+128
\|
*	match rails console environment support, to server	schneems	2012-03-22	1	-0/+19
\| \| \| \|	rails server takes `-e` as an argument to specify RAILS_ENV, rails console currently does not have the same interface. This commit fixes this disparity so developers can manually specify `RAILS_ENV` or can pass in an environment with a `-e`.
*	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
*	Fix tests, Rails.env may be different on CI	Piotr Sarnacki	2012-02-16	1	-2/+5
\|
*	Refactor Rails::Console to make it easier to test and add tests for it	Piotr Sarnacki	2012-02-16	1	-0/+84