Merge pull request #1147 from dhensby/patch-1

Change to how environment file is found
This commit is contained in:
Ingo Schommer 2013-01-30 07:24:49 -08:00
commit f633a72921

View File

@ -56,10 +56,8 @@ of `$databaseConfig` and `Director::set_dev_servers`, and instead make sure that
The mechanism by which the `_ss_environment.php` files work is quite simple. Here's how it works: The mechanism by which the `_ss_environment.php` files work is quite simple. Here's how it works:
* At the beginning of SilverStripe's execution, the `_ss_environment.php` file is searched for, and if it is found, it's * At the beginning of SilverStripe's execution, the `_ss_environment.php` file is searched for, and if it is found, it's
included. SilverStripe looks in 3 places for the file: included. SilverStripe looks in all the parent folders of framework up to the server root (using the REAL location of
* The site's base folder (ie, a sibling of framework, jsparty, and cms) the dir - see PHP realpath()):
* The parent of the base folder
* The grandparent of the base folder
* The `_ss_environment.php` file sets a number of "define()". * The `_ss_environment.php` file sets a number of "define()".
* "conf/ConfigureFromEnv.php" is included from within your `mysite/_config.php`. This file has a number of regular * "conf/ConfigureFromEnv.php" is included from within your `mysite/_config.php`. This file has a number of regular
configuration commands that use those defines as their arguments. If you are curious, open up configuration commands that use those defines as their arguments. If you are curious, open up