env VS viper

It seems https://github.com/caarlos0/env does all of that too, have you tried it?

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.

I'll also add that we set our configuration as structs, and use https://github.com/spf13/viper to load the structure from TOML.

Configuration file parsing viper

I've created a bare-bones cli-project tthat uses cobra for cli-args and viper for configuration-management. Currently the application only has a single flag --user (or -u) and prints the passed argument to the console:

https://github.com/joho/godotenv - load env file (or sometimes https://github.com/spf13/viper or load https://github.com/yosuke-furukawa/json5 directly)

I’ll be honest, I prefer urfave/cli over cobra generally speaking. Not for any reason outside of personal preference due to development experience. urfave/cli just feels more intuitive to me. However, if I’m building a CLI tool with really complex configuration, I’ll typically choose cobra and pair it with viper to make sure handling config loading is done properly. Both cobra and viper were written by the same person (and both widely used in production in conjunction with each other), so I trust they’ll play nicely.

It can be easily used with https://pkg.go.dev/flag or https://github.com/spf13/viper (for configuration) and even https://github.com/stretchr/testify (for asserting)

I'd recommend checking out https://github.com/spf13/viper for configurations and https://github.com/rs/zerolog for enhanced logging.

Advanced config management with viper and useful config commands such as setting or getting config values directly from CLI (like this config set -k logs.write -v true ). ENV & File (TOML or YAML) based configuration. Configuration is self-documented, simple type config info to show every config field available with description for each, so no need to write a whole wiki page to explain what each setting does.

config.go - Handles the configuration part (in our case, the key environment variable) with help from Viper;

I contribute to open source projects as well - in various ways - and it's fine for a maintainer of a huge project to use that wording.

He pushed hugo and viper in 2013-2014: https://github.com/gohugoio/hugo/commits/v0.7, viper: https://github.com/spf13/viper/commit/98be071

Steve is a very accomplished programmer, with what hugo / viper became in the go ecosystem by itself. In my view, the projects also jumpstarted a lot of new users who were trying out golang who weren't sold on it yet. I didn't really appreciate his leadership or advisory roles until now, that's just icing on the cake.

Thanks for your contributions, Steve!