- 02 8月, 2010 2 次提交
-
-
由 Fred Wu 提交于
Improved how AppGenerator generates the application name. It now detects the current app name whenever possible. This means that renaming the residing directory will not effect the app name generated by AppGenerator. [#5225 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 rohit 提交于
-
- 30 7月, 2010 1 次提交
-
-
由 Steve Agalloco 提交于
[#5245 state:committed] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
- 26 7月, 2010 2 次提交
-
-
由 José Valim 提交于
-
由 Xavier Noria 提交于
application generation: --skip-testunit and --skip-activerecord renamed to --skip-test-unit and --skip-active-record respectively Reason is their proper spellings are "Test::Unit" and "Active Record". Option names and descriptions have been revised, as well as some method names and minor details here and there.
-
- 17 7月, 2010 2 次提交
-
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
- 25 6月, 2010 1 次提交
-
-
由 Prem Sichanugrist 提交于
It turned out to be that scaffold for singeleton resource will always depend on another model, and it's not possible at the moment to make the application tests pass after generate the singeleton scafold. So, it would be better to remove it for now and probably provide another generator, such as singeleton_scaffold, in which also require the depended model name. [#4863 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 24 6月, 2010 1 次提交
-
-
由 Xavier Noria 提交于
-
- 23 6月, 2010 1 次提交
-
-
由 Mohammed Siddick.E 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 20 6月, 2010 2 次提交
-
-
由 rohit 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 13 6月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 12 6月, 2010 1 次提交
-
-
由 Damien Mathieu 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 11 6月, 2010 2 次提交
-
-
由 Santiago Pastorino 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 Jeff Kreeftmeijer 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 08 6月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 03 6月, 2010 3 次提交
-
-
由 José Valim 提交于
Still copy application configuration to generator even if they are required earlier. Also tidy up the guide a little bit.
-
由 José Valim 提交于
-
由 wycats 提交于
If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
-
- 02 6月, 2010 1 次提交
-
-
由 José Valim 提交于
Still copy application configuration to generator even if they are required earlier. Also tidy up the guide a little bit.
-
- 30 5月, 2010 2 次提交
-
-
由 José Valim 提交于
-
由 wycats 提交于
If you have existing Metals, you have a few options: * if your metal behaves like a middleware, add it to the middleware stack via config.middleware.use. You can use methods on the middleware stack to control exactly where it should go * if it behaves like a Rack endpoint, you can link to it in the router. This will result in more optimal routing time, and allows you to remove code in your endpoint that matches specific URLs in favor of the more powerful handling in the router itself. For the future, you can use ActionController::Metal to get a very fast controller with the ability to opt-in to specific controller features without paying the penalty of the full controller stack. Since Rails 3 is closer to Rack, the Metal abstraction is no longer needed.
-
- 17 5月, 2010 1 次提交
-
-
由 Simon Jefford 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 16 5月, 2010 2 次提交
-
-
由 José Valim 提交于
-
由 Jeff Kreeftmeijer 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 15 5月, 2010 1 次提交
-
-
由 Adrian Sanchez 提交于
Bundler deprecated options in Gemfile with application template using method "gem" [#4534 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 06 5月, 2010 1 次提交
-
-
由 Carl Lerche 提交于
-
- 01 5月, 2010 2 次提交
- 30 4月, 2010 4 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 Carlhuda 提交于
-
由 José Valim 提交于
-
- 29 4月, 2010 1 次提交
-
-
由 Ravinder Singh 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 19 4月, 2010 1 次提交
-
-
由 Phil Smith 提交于
In the event a migration already exists with that number, the new migration's timestamp will be incremented by 1. [#4412 state:resolved] Signed-off-by: NMichael Koziarski <michael@koziarski.com>
-
- 12 4月, 2010 1 次提交
-
-
由 Andrew White 提交于
Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 10 4月, 2010 2 次提交
-
-
由 Jeremy Kemper 提交于
This reverts commit ea2c5fa8. Conflicts: railties/lib/rails/generators/rails/app/templates/app/views/layouts/application.html.erb railties/test/generators/app_generator_test.rb
-
由 Jeremy Kemper 提交于
-
- 06 4月, 2010 1 次提交
-
-
由 José Valim 提交于
-