alternative defaults: .env.defaults

[falkenhawk]

I have a use case where I can't use .env file as defaults easily, without intricate measures, transition periods, automated scripts migrating .env to .env.local etc. (migrating from dotenv on a shared repo with multiple devs constantly working on it)

I can expect that it might be difficult to convince you to add this feature, I tried to explain the reasoning, but I am not too good at writing docs - so if you find this useful, any suggestions how to describe it better would be very welcome...

Below is the new paragraph from README:

---

Alternative defaults: .env.defaults

In addition to .env, you may also use .env.defaults to store default (fallback) values.

This may come handy e.g. when migrating from dotenv (where it is strongly advised against committing .env file to VCS)
and you already have .env file used to store your local values.

In such case, you may prefer to keep using your existing .env (ignored by VCS) as your local config
and create additional .env.defaults (tracked by VCS) file which will be loaded before .env.

Then at every place .env is mentioned in the docs, read it as: ".env.defaults first, then .env".

[kerimdzhanov]

Hey Maciej,

That is an excellent point! I will release a new version with this feature soon.

Thanks for your contributions to the project, it's much appreciated!

[falkenhawk]

I'm glad you like it! It's a pleasure :)