- 13 6月, 2010 1 次提交
-
-
由 Santiago Pastorino 提交于
-
- 12 6月, 2010 1 次提交
-
-
由 Xavier Noria 提交于
-
- 11 6月, 2010 3 次提交
-
-
由 Xavier Noria 提交于
-
由 Neeraj Singh 提交于
-
由 Xavier Noria 提交于
-
- 09 6月, 2010 1 次提交
-
-
由 Xavier Noria 提交于
-
- 08 6月, 2010 1 次提交
-
-
由 Mikel Lindsaar 提交于
-
- 07 6月, 2010 3 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
-
- 05 6月, 2010 3 次提交
-
-
由 Xavier Noria 提交于
-
由 Xavier Noria 提交于
removes Array#random_element and backports Array#sample from Ruby 1.9, thanks to Marc-Andre Lafortune
-
由 Mikel Lindsaar 提交于
Signed-off-by: NDavid Heinemeier Hansson <david@loudthinking.com>
-
- 03 6月, 2010 14 次提交
-
-
由 Mikel Lindsaar 提交于
-
由 José Valim 提交于
Still copy application configuration to generator even if they are required earlier. Also tidy up the guide a little bit.
-
由 Xavier Noria 提交于
-
由 eparreno 提交于
-
由 eparreno 提交于
-
由 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.
-
由 Josiah Ivey 提交于
-
由 Ryan Bigg 提交于
Cover more of the Rails initialization process, regarding the internals of YourApp::Application inheritance from Rails::Application and more.
-
由 Jaime Iniesta 提交于
-
由 Jaime Iniesta 提交于
-
由 Jaime Iniesta 提交于
-
由 Rohit Arondekar 提交于
-
由 eparreno 提交于
-
由 eparreno 提交于
-
- 02 6月, 2010 2 次提交
-
-
由 José Valim 提交于
Still copy application configuration to generator even if they are required earlier. Also tidy up the guide a little bit.
-
由 Xavier Noria 提交于
-
- 31 5月, 2010 1 次提交
-
-
由 eparreno 提交于
-
- 30 5月, 2010 1 次提交
-
-
由 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.
-
- 28 5月, 2010 1 次提交
-
-
由 eparreno 提交于
-
- 25 5月, 2010 5 次提交
-
-
由 Josiah Ivey 提交于
-
由 Ryan Bigg 提交于
Cover more of the Rails initialization process, regarding the internals of YourApp::Application inheritance from Rails::Application and more.
-
由 Jaime Iniesta 提交于
-
由 Jaime Iniesta 提交于
-
由 Jaime Iniesta 提交于
-
- 21 5月, 2010 1 次提交
-
-
由 Rohit Arondekar 提交于
-
- 19 5月, 2010 2 次提交
-
-
由 Josiah Ivey 提交于
-
由 Josiah Ivey 提交于
-