tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #7638 from kinglozzer/kinglozzer-patch-1

Browse Source 
Update docs for .env files to explicitly mention naming convention
This commit is contained in:
Chris Joe 2017-11-25 01:10:54 +13:00 committed by GitHub
commit e991792179
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/en/00_Getting_Started/03_Environment_Management.md
View File

@ -21,9 +21,11 @@ webserver.
## Managing environment variables with `.env` files
By default the `.env` must be placed in your project root (ie: same folder as you `composer.json`) or the parent
By default a file named `.env` must be placed in your project root (ie: the same folder as your `composer.json`) or the parent
directory. If this file exists, it will be automatically loaded by the framework and the environment variables will be
set. An example `.env` file is included in the default installer named`.env.example`.
set. An example `.env` file is included in the default installer named `.env.example`.
**Note:** The file must be named exactly `.env` and not any variation (such as `mysite.env` or `.env.mysite`) or it will not be detected automatically. If you wish to load environment variables from a file with a different name, you will need to do so manually. See the [Including an extra `.env` file](#including-an-extra-env-file) section below for more information.
## Managing environment variables with Apache