aboutsummaryrefslogtreecommitdiffstats
path: root/railties/guides/source/configuring.textile
Commit message (Collapse)AuthorAgeFilesLines
* prefer %Q() over escaped double quotesXavier Noria2010-07-271-1/+1
|
* Fixed field_error_proc default example on guidesArkadiusz Holko2010-07-261-1/+1
|
* [PATCH] Update guides after Jeremy Kemper's changes on fieldWithErrorsIvan Torres2010-07-221-1/+1
| | | | to field_with_errors [#157 state:resolved]
* Fix minor typos and inconsistencies, and one minor grammar changerspeicher2010-06-141-6/+6
|
* Removing Metal from Rails 3. wycats2010-05-291-2/+0
| | | | | | | | | | | | | | | | | | | | 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.
* Replace 'RAILS_ROOT' to 'Rails.root' and 'RAILS_ENV' to 'Rails.env' in ↵Anil Wadghule2010-04-121-1/+1
| | | | significant places.
* Fix configuring guide to validate XHTML 1.0 StrictJaime Iniesta2010-04-061-1/+1
|
* preinitializer.rb is no longer needed, so remove it from the guide and ↵wycats2010-03-281-9/+7
| | | | replace with better suggestion. [#4279 state:resolved]
* Updated asset_template_path to asset_path and have it also support a String ↵wycats2010-03-281-1/+1
| | | | [#4247 state:resolved]
* Allow customisation of asset path generation using a proc.Craig R Webster2010-03-281-0/+2
| | | | | | | | | | | | | | | | Set config.action_controller.asset_path_template to a proc that takes one argument - the direct, unchanged asset path - and returns a path to that asset using the scheme that your assets require. This is useful if you have a setup which scales by introducing new application servers where the mtime of the asset files may not be the same as those of the asset files on your previous servers, but it does require your web servers to have knowledge of the asset template paths that you rewrite to so it's not suitable for out-of-the-box use. An example of configuring asset path generation and rewriting these paths using Apache is included in actionpack/lib/action_view/helpers/asset_tag_helper.rb. Signed-off-by: wycats <wycats@gmail.com>
* Fix Sam Ruby's tests and deprecation warningsCarlhuda2010-03-041-1/+1
|
* Merge docrailsPratik Naik2010-01-171-59/+115
|
* Merge docrailsPratik Naik2009-07-251-1/+1
|
* Merge with docrailsPratik Naik2009-02-241-5/+5
|
* Merge docrails along with the new guides and guides generation codePratik Naik2009-02-061-0/+234