Documentation updates: .env question

[danenania]

Hey @SeriousM, I'm working on beefing up the documentation to make it consistent with others, and had a question: is the package attempting to load a .env file from the project root before executing the envkey binary? I didn't see this in a quick scan of the code, so I wanted to check.

If not, could we add this step, perhaps with a package like this one for the sake of consistency?

[SeriousM]

Hey Dane! The package doesn't do that by itself. We could add the functionality but not right now as this needs some deeper thoughts about where to find the .env file. In dotnet we don't always know where the codebase lies and this needs a understandable interface to the user. Tahnk you for your work!

[SeriousM]

Btw, the package supports windows (x64) as well as linux.

[danenania]

Ok thanks. There was a similar issue of determining project root in envkey-python, which was solved with a os.getcwd() call, which gives whatever directory the current process is started from.

From this SO thread it seems that either System.IO.Directory.GetCurrentDirectory(); or System.IO.Path.GetDirectoryName(System.Windows.Forms.Application.ExecutablePath); could have potential?

[SeriousM]

The point here is that dotnet can not only be executed as standard executable but as windows service, in iis as embedded executable or as web application, as Azure function, with the help of the dotnet runtime and other wonderful ways. I want to find an easy way to let the user choose which environment is currently executed. A simple SO check is not enough here.

…

On Wed, 16 Jan 2019, 20:42 Dane Schneider ***@***.*** wrote: Ok thanks. There was a similar issue of determining project root in envkey-python, which was solved with a os.getcwd() call, which gives whatever directory the current process is started from. From this SO thread <https://stackoverflow.com/questions/21726088/how-to-get-current-working-directory-path-c> it seems that either System.IO.Directory.GetCurrentDirectory(); or System.IO.Path.GetDirectoryName(System.Windows.Forms.Application.ExecutablePath); could have potential? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAcMvWgpzlP35s65wRcTwMDStXaCC5R-ks5vD4CtgaJpZM4aDkTD> .

[danenania]

I see, but in these situations where there is no simple concept of a 'root directory' then it's fine if we just don't find a .env, since we'll still check for the ENVKEY environment variable as you're already doing. The main use of the .env is in development, so as long it would find the .env file in most common development use cases, that would be sufficient.