viper VS kelseyhightower/envconfig

Viper is a configuration management library that handles environment variables, config files, and command-line flags. It supports JSON, YAML, TOML, and more, making it easy to manage settings in one place.

5. Viper

Managing configurations efficiently is a cornerstone of building scalable and maintainable software. In Go, the Viper package 🐍 stands out as a robust solution for managing application configurations. With support for multiple file formats, environment variables, and seamless unmarshaling to structs, Viper simplifies configuration management for modern applications.

- Terminal-Based Workflow: CREV is a CLI tool, removing the need to switch between your editor and the browser.

I have written the CREV CLI tool in Go as I was interested in learning the language and I heard many good things about it’s efficiency and speed. I used https://github.com/spf13/cobra to manage the CLI commands and [Viper](https://github.com/spf13/viper) for handling configurations. This is the first project I have done with Go but I find the language interesting and the Go routines also help with reading in your entire codebase. For the code reviews themselves I use google cloud functions which invoke GPT-4o (am also planning to add Claude 3.5 and GPT-o1).

I’d love to hear your feedback—whether it’s ideas for new features or reasons why you believe this tool is useful or useless to you. I am using it daily so it at least solved my own problem :)

Environment variables: using Viper

Once environment variables are setup we need load them into our project. For this this i will use viper

The code uses Viper to load configuration files in the application.

github.com/spf13/viper

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)