From 6a5c8b91998c56e50b5cc934d968947cd319f735 Mon Sep 17 00:00:00 2001 From: Vipul A M Date: Mon, 25 Mar 2019 03:14:51 +0530 Subject: Cleanup guide for configuring config.disable_sandbox and related changelog [ci skip] (#35733) --- guides/source/configuring.md | 2 +- railties/CHANGELOG.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/guides/source/configuring.md b/guides/source/configuring.md index 448c02425f..ed739aa0ab 100644 --- a/guides/source/configuring.md +++ b/guides/source/configuring.md @@ -86,7 +86,7 @@ application. Accepts a valid week day symbol (e.g. `:monday`). end ``` -* `config.disable_sandbox` controls whether or not someone could start a console in sandbox mode, as a long session of sandbox console could lead database server to run out of memory. +* `config.disable_sandbox` controls whether or not someone can start a console in sandbox mode. This is helpful to avoid a long running session of sandbox console, that could lead a database server to run out of memory. Defaults to false. * `config.eager_load` when `true`, eager loads all registered `config.eager_load_namespaces`. This includes your application, engines, Rails frameworks, and any other registered namespace. diff --git a/railties/CHANGELOG.md b/railties/CHANGELOG.md index cad5ae02a8..9d026ad4fd 100644 --- a/railties/CHANGELOG.md +++ b/railties/CHANGELOG.md @@ -1,8 +1,8 @@ * Add `config.disable_sandbox` option to Rails console. This setting will disable `rails console --sandbox` mode, preventing - developer from accidentally starting a sandbox console, left it inactive, - and cause the database server to run out of memory. + developer from accidentally starting a sandbox console, + which when left inactive, can cause the database server to run out of memory. *Prem Sichanugrist* -- cgit v1.2.3