mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
9cfeefb637
* 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. |
||
---|---|---|
.. | ||
bin | ||
lib | ||
test | ||
activesupport.gemspec | ||
CHANGELOG | ||
install.rb | ||
MIT-LICENSE | ||
Rakefile | ||
README |
= Active Support -- Utility classes and standard library extensions from Rails Active Support is a collection of various utility classes and standard library extensions that were found useful for Rails. All these additions have hence been collected in this bundle as way to gather all that sugar that makes Ruby sweeter. == Download The latest version of Active Support can be found at * http://rubyforge.org/project/showfiles.php?group_id=182 Documentation can be found at * http://as.rubyonrails.com == Installation The preferred method of installing Active Support is through its GEM file. You'll need to have RubyGems[http://rubygems.rubyforge.org/wiki/wiki.pl] installed for that, though. If you have it, then use: % [sudo] gem install activesupport-1.0.0.gem == License Active Support is released under the MIT license. == Support The Active Support homepage is http://www.rubyonrails.com. You can find the Active Support RubyForge page at http://rubyforge.org/projects/activesupport. And as Jim from Rake says: Feel free to submit commits or feature requests. If you send a patch, remember to update the corresponding unit tests. If fact, I prefer new feature to be submitted in the form of new unit tests. For other information, feel free to ask on the ruby-talk mailing list (which is mirrored to comp.lang.ruby) or contact mailto:david@loudthinking.com.