VL.IO.DotEnvFile
0.0.3
dotnet add package VL.IO.DotEnvFile --version 0.0.3
NuGet\Install-Package VL.IO.DotEnvFile -Version 0.0.3
<PackageReference Include="VL.IO.DotEnvFile" Version="0.0.3" />
<PackageVersion Include="VL.IO.DotEnvFile" Version="0.0.3" />
<PackageReference Include="VL.IO.DotEnvFile" />
paket add VL.IO.DotEnvFile --version 0.0.3
#r "nuget: VL.IO.DotEnvFile, 0.0.3"
#:package VL.IO.DotEnvFile@0.0.3
#addin nuget:?package=VL.IO.DotEnvFile&version=0.0.3
#tool nuget:?package=VL.IO.DotEnvFile&version=0.0.3
VL.IO.DotEnvFile
Small wrapper for https://github.com/nozzlegear/dotenvfile to work with vvvv-gamma
Installation
nuget install VL.IO.DotEnvFile
About
A .env file, used to store environment variables, e.g. variables defined per environment, such maybe database url, database password, any sensitive information, that should be available as early as possible during startup, and should not be leaked away. Normally .env should always be added to .gitignore, instead you should provide an .env-example with definitions of variables one expect. You can continue reading this article.
.env originating from nodejs you can check dotenv#rules for .env rules. (Hope some of theme work)
Original usage of .env file, is to allow to run application in multiple CICD environments, e.g. tests, satage, prod. So you can have your secrets stored and setted up explicitly per environment...
Contrubuting
The original DotEnvFile provides methods like:
DotEnvFile.InjectIntoEnvironment(System.EnvironmentVariableTarget.Process, variables);
Witch were not including in initial release. If one would like to include this, we would gladly accept PR's starting with feat/ feature, or fix/ for a bug fix.
Credits
Learn more about Target Frameworks and .NET Standard.
-
- DotEnvFile (>= 2.1.0)
- FSharp.Core (>= 8.0.403)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.