From a83edb5a131a4ac91d27c7b7920225d9399e7b5a Mon Sep 17 00:00:00 2001 From: Adam Kudrna Date: Wed, 20 Dec 2023 19:28:25 +0100 Subject: [PATCH] Create `.env` file automatically after `npm install` (don't overwrite if already exists) --- CONTRIBUTING.md | 11 +---------- package.json | 1 + 2 files changed, 2 insertions(+), 10 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9f29881d..5d068d20 100644 --- a/CONTRIBUTING.md +++ b/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 diff --git a/package.json b/package.json index 363ee81d..6ccb038d 100644 --- a/package.json +++ b/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",