Recursively find .env files in your current project and use them to populate you environment.
The package works very similarly to go-env,
where environment variables can be loaded into the application's runtime
environment through the definition of a .env or .env.* file. However, this
package supports a recursive autoload up to the calling project's root.
Recursive autoload allows you to, for example, define an .env.test at the
root and a test file at <PROJECT_ROOT>/pkg/some_test.go load the environment
variables correctly.
go get github.com/jmataya/dotenv
Autoloading based on your current working directory can work by importing the following:
import _ "github.com/jmataya/renv/autoload"The most straightforward way to get started is to exactly specify the environment file you want to load.
package main
import "github.com/jmataya/renv"
func main() {
err := renv.LoadEnv("/path/to/env/file")
if err != nil {
// Do something...
}
}In addition to specifying a specific environment file, renv can search for a
file based on a path. FindEnv will search recursively up from a specified
folder to the root of the $GOPATH.
package main
import "github.com/jmataya/renv"
func main() {
envFile, _ := renv.FindEnv("/path/to/search/from")
err := renv.LoadEnv(envFile)
if err != nil {
// Do something...
}
}- Jeff Mataya - @jmataya
Jacques Fuentes @jpfuentes2 has an excellent
package called go-env that I've been
referencing for years. The code for this project is based on go-env and has
modified it to allow for searching .env files.
renv grew out of a desire to take that same functionality and allow executables that may not be at a project root to leverage a project-wide .env file.
MIT