viper VS godotenv

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

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

Create a .env file in root or handle environment variables however you like, we'll use joho/godotenv package.

err := godotenv.Load(): We use the godotenv package to be able to access the variables of the .env locally.

First we will load our envs with the godotenv package, then we start our cognito client, passing the COGNITO_CLIENT_ID, which we got earlier, then we start gin and create a server, that's enough.

Primeiro vamos carregar nossas envs com o pacote godotenv, depois iniciamos nosso cognito client, passando o COGNITO_CLIENT_ID, que pegamos anteriormente, depois iniciamos o gin e criamos um server, isso é o suficiente.

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

In his code it is done using https://github.com/joho/godotenv

envconfig: Library for managing configuration data from environment variables (https://github.com/joho/godotenv)

There is already a more complete, safer and neatly written godotenv alternative. It may be taken as an educational inspiration for next attempts.

Chances are you are going to set them in you real server, and most likely you will going to use Linux for that. So for local development create a .env file with those in there. And at the start of you program, load them. You can use https://github.com/joho/godotenv Don’t share that file of course, and don’t put it in git.