viper VS kelseyhightower/envconfig

Use Viper for config file or environmental variable configuration -- it's going to save you a whole lot of time.

Cobra and Viper.

I've mostly been using https://github.com/spf13/viper of late for my go projects. It supports the standard config formats, (json, yaml, toml etc) and lets you override any value with a ENV value.

Not only that, the "unmarshall to struct" method doesn't work at all for environment variables. https://github.com/spf13/viper/issues/188

IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here

Is this sufficiently better than https://github.com/spf13/viper to warrant a switch?

I'm using https://github.com/spf13/viper for configuration manager.

Ya, I think this issue explains one of the problems: https://github.com/spf13/viper/issues/761

There are some Go packages that can make config easy such as Viper or what I'll do in some of my quick/simple projects is to have a Config struct that I load from a JSON file. You can .gitignore the JSON file, and have your program on first startup write a default JSON file with some sensible default settings (like randomized secret keys for your cookies or JWT tokens and await only your database and email credentials to be filled in).

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.

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)

Additionally I'll use an own Configuration type meant to hold all information my applications needs. I find github.com/kelseyhightower/envconfig to be quite handy when you have to deal with environment variables:

The site deploy functionality is implemented using a small Go program. It performs the deployment using the official Netlify Open API client library from files on a directory. The directory, the site ID, the authentication token, and the rest of the details are configured using environment variables that are picked up using Kelsey Hightower's envconfig library. The program creates a preview site when the environment variable NETLIFY_DRAFT is set.

If you are using only env vars to configure your app I would highly recommend this lightweight library https://github.com/kelseyhightower/envconfig

https://github.com/kelseyhightower/envconfig is also popular