VL.IO.DotEnvFile
0.0.2
See the version list below for details.
dotnet add package VL.IO.DotEnvFile --version 0.0.2
NuGet\Install-Package VL.IO.DotEnvFile -Version 0.0.2
<PackageReference Include="VL.IO.DotEnvFile" Version="0.0.2" />
<PackageVersion Include="VL.IO.DotEnvFile" Version="0.0.2" />
<PackageReference Include="VL.IO.DotEnvFile" />
paket add VL.IO.DotEnvFile --version 0.0.2
#r "nuget: VL.IO.DotEnvFile, 0.0.2"
#:package VL.IO.DotEnvFile@0.0.2
#addin nuget:?package=VL.IO.DotEnvFile&version=0.0.2
#tool nuget:?package=VL.IO.DotEnvFile&version=0.0.2
VL.IO.DotEnvFile
Small wrapper for https://github.com/nozzlegear/dotenvfile to work with vvvv-gamma
Installation
TODO: NUGET
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, yor system should 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 you 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/
bugfix`
Credits
Learn more about Target Frameworks and .NET Standard.
-
- DotEnvFile (>= 2.1.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.