diff options
Diffstat (limited to 'guides/source')
-rw-r--r-- | guides/source/getting_started.md | 2 | ||||
-rw-r--r-- | guides/source/upgrading_ruby_on_rails.md | 24 |
2 files changed, 13 insertions, 13 deletions
diff --git a/guides/source/getting_started.md b/guides/source/getting_started.md index 89b1d3ca03..0cb5d81042 100644 --- a/guides/source/getting_started.md +++ b/guides/source/getting_started.md @@ -68,7 +68,7 @@ The Rails philosophy includes two major guiding principles: again, our code is more maintainable, more extensible, and less buggy. * **Convention Over Configuration:** Rails has opinions about the best way to do many things in a web application, and defaults to this set of conventions, rather than - require that you specify every minutiae through endless configuration files. + require that you specify minutiae through endless configuration files. Creating a New Rails Project ---------------------------- diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md index e3b0f42a95..2ac5a2188b 100644 --- a/guides/source/upgrading_ruby_on_rails.md +++ b/guides/source/upgrading_ruby_on_rails.md @@ -147,18 +147,18 @@ documentation. ### Autoloading is Disabled After Booting in the Production Environment -Autoloading of paths in `config.autoload_paths` is now disabled after booting in -the production environment by default. Eager loading the application is part of -the boot process. Top-level constants should still work as they are still -autoloaded, meaning you don't need to manually require them. - -Constants in deeper places are only executed at runtime, like regular method -bodies. These should also still work because their Ruby definition files will be -eager loaded during the boot process as well. - -For the vast majority of applications this change requires no action. But in the -rare situation where your application needs autoloading in the production -environment, you can set `Rails.application.config.enable_dependency_loading` to +Autoloading is now disabled after booting in the production environment by +default. + +Eager loading the application is part of the boot process, so top-level +constants are fine and are still autoloaded, no need to require their files. + +Constants in deeper places only executed at runtime, like regular method bodies, +are also fine because the file defining them will have been eager loaded while booting. + +For the vast majority of applications this change needs no action. But in the +very rare event that your application needs autoloading while running in +production mode, set `Rails.application.config.enable_dependency_loading` to true. ### XML Serialization |