aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/commands.rb
Commit message (Collapse)AuthorAgeFilesLines
* Use exit(1) instead of exit(false)Philip Arndt2011-01-291-2/+2
|
* Apply exit code 1 when commands don't succeed so that other libraries can ↵Philip Arndt2011-01-291-0/+2
| | | | properly detect the failure.
* Use Rails::Engine.find in commands.rbPiotr Sarnacki2010-12-091-2/+1
|
* Tidy up generators commits.José Valim2010-11-171-4/+1
|
* Do not allow to use plugin_new generator directly, you should use Usage:Piotr Sarnacki2010-11-161-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | rails new APP_PATH [options] Options: -G, [--skip-git] # Skip Git ignores and keeps -r, [--ruby=PATH] # Path to the Ruby binary of your choice # Default: /Users/drogus/.rvm/rubies/ruby-1.8.7-p302/bin/ruby -b, [--builder=BUILDER] # Path to an application builder (can be a filesystem path or URL) [--edge] # Setup the application with Gemfile pointing to Rails repository [--dev] # Setup the application with Gemfile pointing to your Rails checkout [--skip-gemfile] # Don't create a Gemfile -d, [--database=DATABASE] # Preconfigure for selected database (options: mysql/oracle/postgresql/sqlite3/frontbase/ibm_db) # Default: sqlite3 -O, [--skip-active-record] # Skip Active Record files -m, [--template=TEMPLATE] # Path to an application template (can be a filesystem path or URL) -J, [--skip-prototype] # Skip Prototype files -T, [--skip-test-unit] # Skip Test::Unit files Runtime options: -s, [--skip] # Skip files that already exist -p, [--pretend] # Run but do not make any changes -f, [--force] # Overwrite files that already exist -q, [--quiet] # Supress status output Rails options: -v, [--version] # Show Rails version number and quit -h, [--help] # Show this help message and quit Description: The 'rails new' command creates a new Rails application with a default directory structure and configuration at the path you specify. Example: rails new ~/Code/Ruby/weblog This generates a skeletal Rails installation in ~/Code/Ruby/weblog. See the README in the newly created application to get going. command
* Allow running `rails plugin new` command inside rails applicationPiotr Sarnacki2010-11-161-6/+11
|
* Add more information to comments.José Valim2010-09-301-3/+5
|
* Try to guess application's directory while trying to run the server, but ↵Piotr Sarnacki2010-09-301-0/+5
| | | | only if config.ru is not present in current dir
* Allow running generators for Engine with usage of other application.Piotr Sarnacki2010-09-301-1/+11
| | | | | | | | After that commit, developers can set ENGINE_PATH in ENGINE/scripts/rails file and load application's ./script/rails (most of the time it will be dummy application used for testing). When running ./script/rails g it will use application to boot up, but then it will use Engine's root and configuration for generators.
* Add a header that tells Internet Explorer (all versions) to use the best ↵wycats2010-07-271-1/+1
| | | | | | available standards support. This ensures that IE doesn't go into quirks mode because it has been blacklisted by too many users pressing the incompatible button. It also tells IE to use the ChromeFrame renderer, if the user has installed the plugin. This guarantees that the best available standards support will be used on the client.
* Avoid calls to Rails::Application since this is not the official API.José Valim2010-07-011-5/+5
| | | | Your application should *always* reference your application const (as Blog::Application) and Rails.application should be used just internally.
* Changing command line API from 'rails blog' to 'rails new blog'.Mikel Lindsaar2010-06-041-0/+6
| | | | | | | | | | Also removed the limitation of not being able to call your new server any of the rails commands (generate, server, dbconsole, console etc) as there is no longer any ambiguity here. http://rails.lighthouseapp.com/projects/8994/tickets/4665 Signed-off-by: David Heinemeier Hansson <david@loudthinking.com>
* Ops. Rename performance to profiler.José Valim2010-04-291-1/+1
|
* The rake task :environment now loads config/environment.rb instead of ↵José Valim2010-04-291-54/+48
| | | | initializing the application on its own. This fixes [#4492 state:resolved] and also avoids the application being initialized twice in some rake tasks.
* Load the environment before executing rails console. [#3905 status:resolved]José Valim2010-03-121-1/+1
|
* Revert "Always load the environment before executing any command. [#3905 ↵José Valim2010-03-121-4/+6
| | | | | | status:resolved]" This reverts commit 16846553b8866eab2aa3b128a2a23a221a25f7e3.
* Always load the environment before executing any command. [#3905 ↵José Valim2010-03-121-6/+4
| | | | status:resolved]
* Fix server environment [#3877 status:resolved]Simo Niemelä2010-02-101-2/+5
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* rails runner loads environment after parsing command-line optionsJeremy Kemper2010-02-091-2/+0
|
* Take into account gem versions (so script/rails server can work outside the ↵José Valim2010-02-081-1/+1
| | | | application) and use Rails::Application.root instead of ROOT_PATH.
* server command loads the applicationJeremy Kemper2010-02-041-1/+2
|
* Remove duplicated version check.José Valim2010-02-041-2/+0
|
* -v and --version params now work on rails script in or our of an appMikel Lindsaar2010-02-041-0/+3
|
* Make bin/rails call rails/commands/application, fix generators usage and ↵José Valim2010-02-031-13/+66
| | | | update .gitignores.
* Move railties/lib/* into railties/lib/*Yehuda Katz + Carl Lerche2009-09-241-0/+17
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-02 19:26:51 +0000