Create ignored .env file from template

jaw-sh / stream-nexus

Unified multicast stream chat overlay.

25 stars 8 forks source link

Create ignored .env file from template #11

Closed y-a-t-s closed 10 months ago

y-a-t-s commented 10 months ago

Git currently picks up any changes to .env, and that can cause a lot of problems down the line. I propose tracking a default file which gets copied to the personal .env if it doesn't already exist.

This is important if we start using API keys and secrets. When working with my other branch for handling exchange rate API keys, I had to triple check that I removed my testing key from .env before committing.

y-a-t-s commented 10 months ago

I had the idea that defining a set of key-value pairs with defaults and comparing it with the user's .env file is an objectively much better way to handle it. The mechanism for filling in missing variables allows for updating the user's .env with any new ones that may get added as development progresses.