kelseyhightower/envconfig VS env

To configure the app I'd take a look at https://github.com/kelseyhightower/envconfig

envconfig

- Having one way of configuring the app is excellent. You can either prefer environment variables, a file, or flags. You can do what Viper does by reading the file and unmarshalling it. The built-in flag package is enough for your flag-based config needs. If you want to prefer environment variables, I prefer https://github.com/kelseyhightower/envconfig

To extract values from the system environment, I utilize envconfig, a Go package. Envconfig facilitates mapping system environment variables to a Go struct. These Go structs are exposed through a config package, enabling other parts of the application to access them.

You could prefix your env vars and use this package. https://github.com/kelseyhightower/envconfig

kelseyhightower/envconfig

Pretty much all of our services and pkgs use https://github.com/kelseyhightower/envconfig. It’s dead simple, gets out of your way, and is battle tested

https://github.com/kelseyhightower/envconfig (read config from environment variables, more succinct than viper)

How is this compared to https://github.com/caarlos0/env

One could consider using https://github.com/caarlos0/env instead of the hand-woven

These are a few reasons my team is using https://github.com/caarlos0/env

Consider something like this library that allows loading of environment variables into a struct.

The pattern with using struct tags was inspired by the eminent module env (https://github.com/caarlos0/env).

https://github.com/caarlos0/env.

How does it compare with https://github.com/caarlos0/env ?

I also have been using https://github.com/caarlos0/env in all projects since that was the one which I used in first project.