Create .env file automatically after npm install (don't overwrite…

… if already exists)

CONTRIBUTING.md

@@ -15,16 +15,7 @@ This allows running the documentation site which serves as a development platfor
 
 Review the default env variable values in the `docker-compose.yml` file.
 The defaults should work for most systems, but can be changed if needed.
-
-To change them:
-
-1. Create a `.env` file from the template:
-
-    ```bash
-    cp .env.dist .env
-    ```
-
-2. Edit the new `.env` file as needed
+To change them, edit the `.env` file as needed.
 
 ### Use Docker Compose
 

package.json

@@ -42,6 +42,7 @@
     "lint": "npm run eslint && npm run markdownlint && npm run stylelint",
     "markdownlint": "markdownlint-cli2 \"CONTRIBUTING.md\" \"README.md\" \"RELEASING.md\" \"src/**/*.md\"",
     "postbuild": "npm run copy",
+    "postinstall": "cp -n .env.dist .env || true",
     "precopy": "rm -rf dist && mkdir dist",
     "prepublishOnly": "npm run build",
     "start": "webpack --watch --mode=development",