go-envconfig VS urfave/cli

Also, I put config in the package that needs it using something like this instead of Viper: https://github.com/sethvargo/go-envconfig And then at the entry point make another config that includes all the structs from the packages and inject them after bulk reading in. The beauty of this is I can take a package for reuse and drop it into another project. It’s errors and config are right there with it. Also this reduces cognitive load of trying to find everything in big projects (or dig through a 1000 lines in a centralized location).

Env files are horrible. I recommend https://github.com/sethvargo/go-envconfig

Can you use a framework like urfavecli https://github.com/urfave/cli? This will auto-update every time it detects a new version from your CLI's GitHub repository

I use https://github.com/urfave/cli for local development over cli parameter inside docker over envs

....\Softwares\go\src\prysm\cmd\prysmctl\checkpointsync\cmd.go:3:8: cannot find package "github.com/urfave/cli/v2" in any of:

urfave/cli - A simple, fast, and fun package for building command line apps in Go;

and probably something else will be added in the future. The final kind of launch command would like to see such djob [options] - command. Command is the command (with arguments to run). -- should separate the arguments of the utility from the arguments of the program to run. There are several excellent solutions for working with command-line arguments, such as spf13/cobra or urfave/cli. But they’re good for building an interface out of a lot of commands, and for one (as in my example) they’re redundant. So I used the flag library. I have defined the following structure with arguments:

There are alternatives available for Cobra as well i.e. mitchellh/cli, go-flags, urfave/cli etc.

https://github.com/urfave/cli - A Golang package used to structure the CLI.