aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/commands
Commit message (Collapse)AuthorAgeFilesLines
* remove references to *::VERSION, replace with *.versionCharlie Somerville2013-03-211-1/+1
|
* More helpful message when starting serverGabe Kopley2013-03-181-1/+1
| | | | v2 of pull request based on feedback from @rafaelfranca, @schneems, and @carlosantoniodasilva
* config.ru uses the effective Rack appYves Senn2013-03-151-0/+1
| | | | | | | | | | We used to pass the Rails::Application subclass to #run. The Rails server then called #to_app to convert that class to the actual Rack application. if you surround `#run` with a call to `#map` the server no longer convertes the class to the instance and we end up with unnecessary delegation calls on every request.
* Stop calling "super" twice in Rails::Server#appCarlos Antonio da Silva2013-03-121-1/+4
| | | | Cache the value of "super" in a variable and use it instead.
* Make sure that `rails test` load test in test envPrem Sichanugrist2013-03-091-3/+9
|
* Improve wording for rails test commandDalibor Nasevic2013-03-091-17/+17
|
* Load fixtures only when running suites, or `-f`Prem Sichanugrist2013-03-091-1/+18
| | | | | | * `rails test -f` will run the test suites with all fixtures loaded * New application will now generated without `fixtures :all` line enabled by default.
* Add support for MiniTest flags in TestRunnerPrem Sichanugrist2013-03-091-30/+61
| | | | | Any flags that got set will be passed through to MiniTest::Unit.runner, such as `-n`, `-s-, and `-v`.
* Add `rails test` command to run the test suitePrem Sichanugrist and Chris Toomey2013-03-091-0/+92
| | | | | | | | | | | | | | | | | | | To run the whole test suite: $ rails test To run the test file(s): $ rails test test/unit/foo_test.rb [test/unit/bar_test.rb ...] To run the test suite $ rails test [models,helpers,units,controllers,mailers,...] For more information, see `rails test --help`. This command will eventually replacing `rake test:*`, and `rake test` command will actually invoking `rails test` instead.
* Fix rails console --sandboxJon Leighton2013-03-081-1/+3
| | | | | | I've also added a proper acceptance test which reproduced the issue. Closes #9513, #9515.
* Use --rc= instead of --rcrobertomiranda2013-02-041-2/+6
|
* Refactor --rc optionGuillermo Iguaran2013-02-021-6/+1
|
* Add --rc option to support the load of a custom rc fileAmparo Luna2013-02-011-1/+7
|
* Prefer File.read over File.open.readAkira Matsuda2013-02-011-1/+1
|
* Add --no-rc option to skip the loading of railsrc fileAmparo Luna2013-01-311-6/+8
|
* extract PerformanceTest into rails-performance_tests gemYves Senn2013-01-102-66/+0
|
* Introduce ./bin for your app's executables: bin/bundle, bin/rails, bin/rake. ↵Jeremy Kemper2013-01-061-1/+1
| | | | Executable scripts are versioned code like the rest of your app. To generate a stub for a bundled gem: 'bundle binstubs unicorn' and 'git add bin/unicorn'
* Rescue from LoadError when trying to load the debugger gem for consoleCarlos Antonio da Silva2013-01-061-1/+1
| | | | | | | | Avoid swallowing all exceptions that might happen when requiring debugger, just catch a LoadError if it cannot be loaded. Check for more background: https://github.com/rails/rails/commit/28fd867c9bc790636d37a28f288791cd0089a6fd#commitcomment-2386952
* Don't use Rails.root since it is not available at this pointRafael Mendonça França2013-01-052-2/+2
|
* Remove unnecessary begin..rescue..end, use only rescueCarlos Antonio da Silva2013-01-041-7/+5
|
* Move class method to instance in dbconsoleCarlos Antonio da Silva2013-01-042-2/+3
| | | | | This method doesn't need to be in the class, since it's only used only from the instance.
* This commit fixes issue #8628Mykola Kyryk2013-01-042-2/+19
| | | | | | | | | | | | Allow environment name to start with a substring of the default environment names. For example: tes, pro, prod, dev, devel, etc. Fixing identation. Adding test for Rails::Console.parse_arguments method. Fix issue 8628 for Rails::DBConsole.
* Explicit options should have precedence over railsrc on the `rails new`Rafael Mendonça França2012-12-241-2/+1
| | | | | | command Closes #8545
* Add ENV['RACK_ENV'] support to rake runner/console/server.kennyj2012-12-063-3/+3
|
* Fix wrong doc and message about rails profiler.kennyj2012-12-041-1/+1
|
* Refactor config abort message a bit for dbconsoleCarlos Antonio da Silva2012-11-182-8/+4
| | | | | | Remove not used variable. Remove config attr_reader causing warning. Fix indent in runner file.
* Fix rails db command with sqlite3 databaseCarlos Antonio da Silva2012-11-181-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | When using sqlite3 it was attempting to find the database file based on Rails.root, the problem is that Rails.root is not always present because we try to first manually load "config/database.yml" instead of loading the entire app, to make "rails db" faster. This means that when we're in the root path of the app, calling "rails db" won't allow us to use Rails.root, making the command fail for sqlite3 with the error: ./rails/commands/dbconsole.rb:62:in `start': undefined method `root' for Rails:Module (NoMethodError) The fix is to simply not pass any dir string to File.expand_path, which will make it use the current directory of the process as base, or the root path of the app, which is what we want. When we are in any other subdirectory, calling "rails db" should work just fine, because "config/database.yml" won't be found, thus "rails db" will fallback to loading the app, making Rails.root available. Closes #8257.
* Removing warning : assigned but unused variableArun Agrawal2012-11-101-1/+1
|
* copy the log level from the config settingsAaron Patterson2012-11-091-0/+1
|
* Use Ruby 1.9 Hash syntax in railtiesRobin Dupret2012-10-145-11/+11
|
* update Rails::Generators docs [ci skip]Francesco Rodriguez2012-10-071-1/+1
|
* Support MySQL SSL in rails dbconsole.needfeed2012-09-101-1/+6
|
* add Rack::Lock for webrickAaron Patterson2012-08-211-0/+9
|
* removes usage of Object#in? from the code base (the method remains defined ↵Xavier Noria2012-08-062-4/+2
| | | | | | | | | | | | | | | | | | | by Active Support) Selecting which key extensions to include in active_support/rails made apparent the systematic usage of Object#in? in the code base. After some discussion in https://github.com/rails/rails/commit/5ea6b0df9a36d033f21b52049426257a4637028d we decided to remove it and use plain Ruby, which seems enough for this particular idiom. In this commit the refactor has been made case by case. Sometimes include? is the natural alternative, others a simple || is the way you actually spell the condition in your head, others a case statement seems more appropriate. I have chosen the one I liked the most in each case.
* Remove support for rails server RAILS_ENV=env-nameSam Oliver2012-05-301-5/+0
|
* Fix various bugs with console arguments.Sam Oliver2012-05-302-85/+100
| | | | Allow hyphens in environment names again.
* Add support runner hook.kennyj2012-05-291-0/+1
|
* use File.join rather than depend on PathnameAaron Patterson2012-05-231-1/+1
|
* Fix `rails db -h` and cosmetic fixes in usage bannersAlexey Vakhov2012-05-223-3/+8
| | | | | | | 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` commandAlexey Vakhov2012-05-221-1/+1
| | | | | | | | | | 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.
* require "rubygems" is obsolete in Ruby 1.9.3Kornelius Kalnbach2012-05-132-3/+0
|
* More faster rails dbconsoleDmitry Vorotilin2012-05-061-10/+28
|
* Add Rails::DBConsole testsAlexey Vakhov2012-05-021-22/+34
|
* Remove unused assignmentsMark Rushakoff2012-04-291-1/+0
|
* and one more timeAditya Sanghi2012-04-242-3/+3
|
* another attempt at the languageAditya Sanghi2012-04-181-1/+1
|
* stamp out ruby-debug19 with extreme prejudice :)Aditya Sanghi2012-04-172-4/+4
|
* match rails console environment support, to serverschneems2012-03-221-0/+13
| | | | 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 variableschneems2012-03-201-0/+5
| | | | | | | 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
* allow people to specify custom formatters, use the default formatter in ↵Aaron Patterson2012-03-121-0/+2
| | | | production so that PID and timestamp are logged. fixes #5388