From f667f0f7ee63a14e600abb0a32446193794c28f1 Mon Sep 17 00:00:00 2001 From: Xavier Noria Date: Mon, 21 Jan 2013 21:14:42 +0100 Subject: [PATCH] copy-edits 7e6e4f2 [ci skip] Capitalization in the title of the section, enumerates the environments in the usual order, adds a paragraph, and tries to use less "you"s. --- guides/source/configuring.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/guides/source/configuring.md b/guides/source/configuring.md index c18cd08264..fc1d0d7530 100644 --- a/guides/source/configuring.md +++ b/guides/source/configuring.md @@ -552,11 +552,13 @@ development: Change the username and password in the `development` section as appropriate. -### Creating Rails environments +### Creating Rails Environments -By default Rails ships with three environments (production, development and test). While these are sufficient for most use cases, there are circumstances when you want more environments. Imagine you have a server, which mirrors the production environment but is only used for testing. You can create a separate environment for this server by creating a file called `config/environments/staging.rb`. This will create a new environment called "staging". You can use the contents of any existing file in `config/environments` as a starting point and make the necessary changes from there. +By default Rails ships with three environments: "development", "test", and "production". While these are sufficient for most use cases, there are circumstances when you want more environments. -After you created the environment file you can now start a server with `rails server -e staging` or a console with `rails console staging` +Imagine you have a server which mirrors the production environment but is only used for testing. Such a server is commonly called a "staging server". To define an environment called "staging" for this server just by create a file called `config/environments/staging.rb`. Please use the contents of any existing file in `config/environments` as a starting point and make the necessary changes from there. + +That environment is no different than the default ones, start a server with `rails server -e staging`, a console with `rails console staging`, `Rails.env.staging?` works, etc. Rails Environment Settings