Add .env file to support storing private data

[edwardhorsford]

Add a .env file for storing private data.

This is created from a template - so the real .env doesn't get committed to git.

This will be useful for teams integrating with APIs - like Notify.

[tvararu]

Looks good to me. 👍

You can force commit an empty .env file to version control. Would that be better than the creation script?

Edit: a small README / documentation blurb informing users that this feature exists could be useful.

[edwardhorsford]

The advantage of the creation script is we can have a bit of a template / defaults - which I feel makes this more approachable.

@joelanman any thoughts on documentation for this? Do you think we could merge (ahead of training on Thursday) and have a think about where docs should go?

[tvararu]

@edwardhorsford no reason not to have that if you commit the initial template to version control. On this branch:

mv lib/template.env .env
git add --force .env

(And revert start.js while keeping the refactored node_modules check)

[edwardhorsford]

I think an advantage to this way of doing things is that if people create their own repos from the kit, when other users download from that repo, they'll too get a template env file.

What do you think?

[tvararu]

@edwardhorsford for that situation it makes sense. Keep it then. 👌