aboutsummaryrefslogtreecommitdiffstats
path: root/railties/lib/rails/railtie
Commit message (Collapse)AuthorAgeFilesLines
* Remove the ability for engines to serve assets from the public directory.José Valim2011-04-151-7/+0
|
* Beef up Rails::Railtie::Configuration docsGabriel Horner2011-03-191-0/+8
|
* Railties typos.R.T. Lechow2011-03-051-1/+1
|
* Remove require AS::Concern from places where is already inSantiago Pastorino2010-12-191-2/+0
|
* Fix indentationSantiago Pastorino2010-12-191-3/+3
|
* Use Concern in Rails::Railtie::ConfigurableSantiago Pastorino2010-12-191-3/+3
|
* Be more explicit about what is deprecated.José Valim2010-10-021-1/+1
|
* Deprecate generators in Railties. You should use app_generators instead.José Valim2010-10-021-26/+6
|
* Added config.app_generators to allow configuring application's generators ↵Piotr Sarnacki2010-09-301-3/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | from railties. With config.generators becomes a way to configure generators for current instance only. For example: module Blog class Engine < Rails::Engine config.generators do |g| g.orm :active_record end config.app_generators do |g| g.test_framework :rspec end end end such definition sets :active_record as orm for engine and :rspec as test_framework for application. The values set with app_generators can be overwritten in application using config.generators as you would normally do: module MyApp class Application < Rails::Application config.generators do |g| g.test_framework :test_unit end end end
* Get rid of static_paths method and instead configure paths for ↵Piotr Sarnacki2010-09-031-0/+8
| | | | ActionDispatch::Static in initializers
* Move singleton pattern to Railtie and remove Engine::Configurable and ↵Piotr Sarnacki2010-09-031-7/+19
| | | | Application::Configurable in favor of unified Railtie::Configurable
* Engine can now serve files with ActionDispatch::StaticPiotr Sarnacki2010-09-031-1/+1
|
* Move AD::Cascade to the bottom of the middleware stack.José Valim2010-05-161-32/+1
|
* Expose remaining hooks to minimize the need for a Railtie based on feedback ↵José Valim2010-05-161-0/+12
| | | | from plugin developers.
* Reorganized initializers a bit to enable better hooks for common cases ↵wycats2010-05-151-6/+42
| | | | | | | | | | | | | | | without the need for Railtie. Specifically, the following hooks were added: * before_configuration: this hook is run immediately after the Application class comes into existence, but before the user has added any configuration. This is the appropriate place to set configuration for your plugin * before_initialize: This is run after all of the user's configuration has completed, but before any initializers have begun (in other words, it runs right after config/environments/{development,production,test}.rb) * after_initialize: This is run after all of the initializers have run. It is an appropriate place for forking in a preforking setup Each of these hooks may be used via ActiveSupport.on_load(name) { }. In all these cases, the context inside the block will be the Application object. This means that for simple cases, you can use these hooks without needing to create a Railtie.
* Move application configuration to the application configuration object, ↵José Valim2010-03-261-69/+8
| | | | remove railtie_name and engine_name and allow to set the configuration object.
* Move middlewares to the Application level. If you want to modify the ↵Carlhuda2010-03-081-4/+0
| | | | middleware, either use Rails.application.config.middleware or modify it in an initializer (if you need to set it relative to user-specified middleware).
* Deprecated ActionController::Base.session_options= and ↵Carlhuda2010-03-041-2/+32
| | | | ActionController::Base.session_store= in favor of a config.session_store method (which takes params) and a config.cookie_secret variable, which is used in various secret scenarios. The old AC::Base options will continue to work with deprecation warnings.
* Move session and session_store onto ActionDispatch and add deprecation warningsCarlhuda2010-03-041-2/+2
|
* No need for a module if it's only being included once into an empty class.Carl Lerche2010-03-041-1/+91
|
* Move configuration to subfolders.José Valim2010-01-232-1/+10
|
* Create configurable modules and ensure that they are added only on direct ↵José Valim2010-01-231-0/+23
children.