.env is created automatically now

kyleshank · Jan 31, 2017 · 944e318 · 944e318
1 parent cd9c547
commit 944e318
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/en/directory-structure.md b/en/directory-structure.md
@@ -40,6 +40,10 @@ This is where all of your Composer dependencies go, including Craft itself, and
 
 This directory represents your web root.
 
+#### `.env`
+
+This is your [PHP dotenv](https://github.com/vlucas/phpdotenv) `.env` configuration file. It defines sensitive or environment-specific config values that don’t make sense to commit to version control.
+
 #### `.env.example`
 
 This is your [PHP dotenv](https://github.com/vlucas/phpdotenv) `.env` file template. It should be used as a starting point for any actual `.env` files, stored alongside it but out of version control on each of the environments your Craft project is running in.

diff --git a/en/installation.md b/en/installation.md
@@ -52,6 +52,7 @@ storage/
 templates/
 vendor/...
 web/...
+.env
 .env.example
 composer.json
 craft
@@ -75,7 +76,7 @@ If you’re given a choice, we recommend the following database settings in most
 - **PostgreSQL**
   - Character Set: `UTF8`
 
-Once the database is created, you’ll need to configure Craft with its connection settings. Copy the `.env.example` file at the root of your Craft project to a new `.env` file, and fill in your database connection settings within it.
+Once the database is created, you’ll need to configure Craft with its connection settings. Open the `.env` file at the root of your Craft project and fill in your database connection settings.
 
 > {tip} That `.env` file will be processed via [PHP dotenv], which the `craftcms/craft` project comes with preinstalled. The advantage of using PHP dotenv is that it offers a place to store sensitive information (like database connection settings) in a file that doesn’t get committed to your Git repository.