yuuza/outline
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update docs to recommend against using .env in prod [ci skip]

Browse Source
This commit is contained in:
Tom Moor
2019-12-05 16:57:17 -08:00
committed by GitHub
parent 9427f06031
commit a2a7f5ef5c
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@@ -53,7 +53,7 @@ For a self-hosted production installation there is more flexibility, but these a
> Requires [Node.js, npm](https://nodejs.org/) and [yarn](https://yarnpkg.com) installed > Requires [Node.js, npm](https://nodejs.org/) and [yarn](https://yarnpkg.com) installed
1. Build the web app with `yarn build:webpack` or `npm run build:webpack` 1. Build the web app with `yarn build:webpack` or `npm run build:webpack`
1. Copy the file `.env.sample` to `.env` and fill out at least the essential fields: 1. Using the `.env.sample` as a reference, set the required variables in your production environment. The following are required as a minimum:
1. `SECRET_KEY` (follow instructions in the comments of `.env`) 1. `SECRET_KEY` (follow instructions in the comments of `.env`)
1. `SLACK_KEY` (this is called "Client ID" in Slack admin) 1. `SLACK_KEY` (this is called "Client ID" in Slack admin)
1. `SLACK_SECRET` 1. `SLACK_SECRET`