env files in production, that's up to you. (You should load env var values during startup or on first access and not look them up more than once during the application's lifetime.)Īdmittedly, this is best practices advice, and if you want to use. This does mean that env vars, and thus this library, are only useful for load time configuration - not anything that changes during the lifetime of an application's run. When the application is deployed into production, actual env vars should be used, not a static. Then every developer gets a copy of that file as part of onboarding that they save into their project dir that uses DotNetEnv to get env vars for configuration. env with localdev testing credentials/etc stored in some secure storage - 1pass/lastpass or s3 bucket or something like that. The purpose of this library is to enable easy local development. A Note about Production and the Purpose of This Library no consistent rules have arisen industry wide yet. env parsing libraries also might have slightly different rules env files.īut then, not all of this is 100% compatible anyway, and that's ok. So this is a convenience feature that will break sourcing. Note that bash env vars do not allow white space pre or post equals, Which might look like it is starting a comment, like: Other than that you do not need to escape single quote chars insideĪ double quoted value, nor double quotes inside single quotes.Īs a special note: if a value is unquoted, it can still include a # char, Special meaning for each of these, in this library, they are all the same, unquoted: can have interpolated variables, but only inline whitespace, and no escaped chars, nor byte code chars.Īs these are the options bash recognizes.'' single: can have whitespace, but no interpolation, no escaped chars, no byte code chars - notably not even escaped single quotes inside - single quoted values are for when you want truly raw values.'' double: can have everything: interpolated variables, plus whitespace, escaped chars, and byte code chars.To load the env vars into a terminal session directly.

Source env file