diff options
author | Alberto Almagro <albertoalmagro@gmail.com> | 2018-06-28 13:18:44 +0200 |
---|---|---|
committer | Alberto Almagro <albertoalmagro@gmail.com> | 2018-07-06 22:46:54 +0200 |
commit | 49e6df35295e4dd5b7603a0f3f4d51c18eac732e (patch) | |
tree | 203e613bce7ed7fa75d39fed59593750cfd54003 | |
parent | 6567464bedd1e39ee7390da9484ba0caa7eb3e07 (diff) | |
download | rails-49e6df35295e4dd5b7603a0f3f4d51c18eac732e.tar.gz rails-49e6df35295e4dd5b7603a0f3f4d51c18eac732e.tar.bz2 rails-49e6df35295e4dd5b7603a0f3f4d51c18eac732e.zip |
Improve text readability
-rw-r--r-- | guides/source/autoloading_and_reloading_constants.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/autoloading_and_reloading_constants.md b/guides/source/autoloading_and_reloading_constants.md index d4b92f12c0..7dc1a5e456 100644 --- a/guides/source/autoloading_and_reloading_constants.md +++ b/guides/source/autoloading_and_reloading_constants.md @@ -472,7 +472,7 @@ default it contains: How files are autoloaded depends on `eager_load` and `cache_classes` config settings which typically vary in development, production, and test modes: * In **development**, you want quicker startup with incremental loading of application code. So `eager_load` should be set to `false`, and Rails will autoload files as needed (see [Autoloading Algorithms](#autoloading-algorithms) below) -- and then reload them when they change (see [Constant Reloading](#constant-reloading) below). - * In **production**, however you want consistency and thread-safety and can live with a longer boot time. So `eager_load` is set to `true`, and then during boot (before the app is ready to receive requests) Rails loads all files in the `eager_load_paths` and then turns off auto loading (NB: autoloading may be needed during eager loading). Not autoloading after boot is a `good thing`, as autoloading can cause the app to be have thread-safety problems. + * In **production**, however, you want consistency and thread-safety and can live with a longer boot time. So `eager_load` is set to `true`, and then during boot (before the app is ready to receive requests) Rails loads all files in the `eager_load_paths` and then turns off auto loading (NB: autoloading may be needed during eager loading). Not autoloading after boot is a `good thing`, as autoloading can cause the app to be have thread-safety problems. * In **test**, for speed of execution (of individual tests) `eager_load` is `false`, so Rails follows development behaviour. What is described above are the defaults with a newly generated Rails app. There are multiple ways this can be configured differently (see [Configuring Rails Applications](configuring.html#rails-general-configuration). |