Added example .env file and tidied up README

[harrymt]

Separated environment bariables into file

• Moved environment variables into separate file .env
• Read these environment variables using dotenv
• Added instructions to create a .env file from an example .env.example file

Tidied up README

• Added link for generating oAuth token
• Link js files when talking about them
• Separated installation/testing/development into sections

[coveralls]

Pull Request Test Coverage Report for Build 36

• 0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 9.756%

---

Totals
Change from base Build 29:	0.0%
Covered Lines:	4
Relevant Lines:	23

---

💛 - Coveralls

[harrymt]

@tailuge I have added a production check, so the .env file is only used during development and not in production / heroku

[tailuge]

Somehow I'm still bothered by the .env file hanging around :) Is the motivation for this making it easier to run in Windows?

[harrymt]

@tailuge fair enough. 😄 The idea behind using a .env file is based on the 12 Factor App.

The key benefits are:

• Cross platform
• Easy to change between deploys without changing any code

Downsides:

• Have to have a .env file hanging around
• Extra setup step instead of passing it into the script
• Have a higher potential to commit these files

[harrymt]

Removed all dotenv stuff, just tidied up README