go-toml VS viper

I wrote one of the Go implementations [0] when TOML was announced and have maintained it since.

As a library implementor, I wish arrays would hold only one type at a time, but I get that could be useful for users. But as a user, I wish tables were fully defined once (more can't be added up later in the file), especially when using larger files.

[0]: https://github.com/pelletier/go-toml

Looks like a it's struggling to install a go dependency, something prob changed since the time this project was made and now. I don't use go but someone more familiar with it can prob help you. Googling the error brought me to this it might solve your problem https://github.com/pelletier/go-toml/discussions/562

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

Instead of directly accessing environment variables with os.Getenv(), integrating a configuration handler like viper might make it maintainable.

I guess most people are using https://github.com/spf13/viper but I don't know if I should read everything from

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.