aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/commands
Commit message (Collapse)AuthorAgeFilesLines
* 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
* Refactor Rails::Console to make it easier to test and add tests for itPiotr Sarnacki2012-02-161-25/+46
|
* Allow to set custom console type with Rails.application.config.console=Piotr Sarnacki2012-02-161-2/+3
| | | | | | | | | | | | | This patch adds ability to set custom console if you want to use something other than IRB. Previously the hack that people used was: silence_warnings do require 'pry' IRB = Pry end which is not the best way to customize things.
* Remove console --irb deprecation noticePiotr Sarnacki2012-02-161-1/+0
|
* broadcasting to the console and remove file tailing middlewareAaron Patterson2012-01-201-1/+7
|
* do not do reverse lookups on incoming requests for webrick. fixes #4542Aaron Patterson2012-01-191-0/+1
|
* fixes in api docsVijay Dev2012-01-132-2/+2
|
* No need to require psych since require yaml does that.Rafael Mendonça França2012-01-041-1/+0
|
* No need to use rescue block to require psychRafael Mendonça França2012-01-041-6/+1
|
* Rails::Plugin has goneSantiago Pastorino2012-01-031-544/+0
|
* gem ruby-debug19 for console error if ruby-debug19 not foundVishnu Atrai2011-12-251-1/+1
|
* Get rid of more 1.8.x dead codeJosé Valim2011-12-201-1/+1
|
* dbconsole: Use the app's database_configuration instead of duplicating code.Dieter Komendera2011-12-141-1/+1
|
* Remove the -h option to dbconsole which is the shorter form of --headerVijay Dev2011-11-221-1/+1
| | | | | | This is done since the -h option to dbconsole hides the conventional -h for help and forces users to use --help to see the usage options for dbconsole.
* Substituted RailsCommands for Rails::CommandsDaniel Dyba2011-11-161-159/+161
|
* Changed Commands module to RailsCommands.Daniel Dyba2011-11-161-3/+3
| | | | | | This is to avoid a conflict that occurs when you add Rake to your Gemfile. There is a Commands Object in Rake that conflicts with the Commands module in plugin.rb. See rails issue #1866.
* Extend IRB right before starting IRB to remove dependency on IRB from ↵Akira Matsuda2011-11-101-0/+2
| | | | Rails::Application
* Use toplevel Rack::ContentLengthJeremy Kemper2011-10-191-1/+1
|
* Use again Rack's ContentLength middleware part 2Santiago Pastorino2011-10-181-0/+1
|
* Use again Rack's ContentLength middlewareSantiago Pastorino2011-10-181-1/+0
|
* Print information about .railsrc to usersGuillermo Iguaran2011-10-021-0/+1
|
* Read extra args for 'rails new' from ~/.railsrcGuillermo Iguaran2011-10-021-0/+7
|
* replace dev.ror.com plugin url with a dummy oneVijay Dev2011-06-161-2/+2
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 23:29:42 +0000