diff options
| author | Ryan Bigg <radarlistener@gmail.com> | 2010-12-02 15:22:25 +1100 |
|---|---|---|
| committer | Ryan Bigg <radarlistener@gmail.com> | 2010-12-02 15:22:25 +1100 |
| commit | 32026b5867182dccbeeefb36728da4b0ce7b8b99 (patch) | |
| tree | 03040a1ad8e4c378a25cf3721cdcf1195103b010 | |
| parent | bde7d2351edf558ff5c2a3fb8d2822d5f8a2ae47 (diff) | |
| download | rails-32026b5867182dccbeeefb36728da4b0ce7b8b99.tar.gz rails-32026b5867182dccbeeefb36728da4b0ce7b8b99.tar.bz2 rails-32026b5867182dccbeeefb36728da4b0ce7b8b99.zip | |
Add mention of config.to_prepare in configuring guide
| -rw-r--r-- | railties/guides/source/configuring.textile | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/railties/guides/source/configuring.textile b/railties/guides/source/configuring.textile index a3e6f0b9be..2482e64f70 100644 --- a/railties/guides/source/configuring.textile +++ b/railties/guides/source/configuring.textile @@ -331,8 +331,9 @@ h3. Initialization events Rails has 4 initialization events which can be hooked into (listed in order that they are ran): * +before_configuration+: This is run as soon as the application constant inherits from +Rails::Application+. The +config+ calls are evaluated before this happens. -* +before_eager_load+: This is run directly before eager loading occurs, which is the default behaviour for the _production_ environment and not for the +development+ enviroment. * +before_initialize+: This is run directly before the initialization process of the application occurs. +* +to_prepare+: Run after the initializers are ran for all Railties, but before eager loading and the middleware stack is built. +* +before_eager_load+: This is run directly before eager loading occurs, which is the default behaviour for the _production_ environment and not for the +development+ enviroment. * +after_initialize+: Run directly after the initialization of the application, but before the application initializers are run. WARNING: Some parts of your application, notably observers and routing, are not yet set up at the point where the +after_initialize+ block is called. |