aboutsummaryrefslogtreecommitdiffstats
path: root/railties/test/application/generators_test.rb
Commit message (Collapse)AuthorAgeFilesLines
* Solve the RAILS_ENV problem in the railties tests in a more generic wayJon Leighton2011-06-061-0/+4
|
* Use load_generators instead.José Valim2011-05-251-4/+2
|
* Fixed failing tests for generators_testArun Agrawal2011-05-251-2/+2
|
* Tidy up generators commits.José Valim2010-11-171-11/+2
|
* Fix generators tests on ruby 1.9Piotr Sarnacki2010-11-171-6/+8
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Do not allow to use plugin_new generator directly, you should use Usage:Piotr Sarnacki2010-11-161-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-0/+6
|
* Provide a cleaner syntax for paths configuration that does not rely on ↵José Valim2010-10-061-1/+1
| | | | method_missing.
* Make config.generators accept string namespaces, you can do now ↵Santiago Pastorino2010-07-211-0/+15
| | | | | | config.generators.test_framework 'rspec' for instance Signed-off-by: José Valim <jose.valim@gmail.com>
* Should call configure! to initiliaze the applicationSantiago Pastorino2010-06-091-0/+1
| | | | Signed-off-by: José Valim <jose.valim@gmail.com>
* Add config.generators.templates to provide alternative paths for template ↵José Valim2010-02-061-11/+4
| | | | lookup.
* Add config.generators.fallbacks.José Valim2010-02-011-1/+12
|
* Move the ActiveRecord generator settings into the RailtieCarl Lerche2010-01-281-1/+1
|
* Test::Unit Railtie Carlhuda2010-01-281-2/+8
|
* Refactor railties test, break huge files in smaller chunks and move ↵José Valim2010-01-261-13/+0
| | | | initializers to application folder.
* Set up subscriber on initialization.José Valim2010-01-131-1/+1
|
* Rename rails.rb -> rails/all.rb and rails/core.rb -> rails.rbCarl Lerche2009-12-311-1/+1
|
* tests pass with requiring the frameworks in rails.rbCarlhuda2009-12-231-14/+16
|
* Remove global Rails initializersCarlhuda2009-12-021-9/+17
|
* Configure generator when needed rather than during initializationJeremy Kemper2009-11-031-1/+2
|
* Pass config.generators options along when RAILS_GENERATORS is set and show ↵José Valim2009-11-031-2/+4
| | | | | | --force-plural message just once. Signed-off-by: Jeremy Kemper <jeremy@bitsweat.net>
* Remove config.gem in favor of using the bundler. This makes config/boot.rb ↵Carl Lerche2009-10-161-0/+1
| | | | | | obsolete. The bundler library is at: http://github.com/wycats/bundler/ and is a rubygem.
* Use Rails.initialize! where we just want to run the initializers and aren't ↵Joshua Peek2009-10-161-2/+2
| | | | concerned about the config
* Deprecate RAILS_ROOT in favor of Rails.root (which proxies to the ↵Carl Lerche2009-10-161-0/+2
| | | | application's object root)
* Have config/application.rb contain the application definition and require ↵Carl Lerche2009-10-151-0/+4
| | | | that file instead of config/boot.rb or config/environment.rb in script/*.
* Finish porting over the initializers to the app object and fix all the testsCarl Lerche2009-10-141-1/+1
|
* Finish porting over the initializers to the app object and fix all the testsCarl Lerche2009-10-081-0/+89