docs VS viper

Google search turned up https://www.mongodb.com/docs/manual/ as the MongoDB user manual.

According to Github, he even contributed to it https://github.com/mongodb/docs/graphs/contributors

There's a lot of evidence that his claims are at least plausible if not credible.

You created a burner account and anonymously keep spreading obscure attacks and lies without any evidence.

The "You may not use or adapt this material for any commercial purpose, such as to create a commercial database or database-as-a-service offering" language suggests that they think the license covers more than just distributing the document, which I believe is an unusual interpretation of what a spec copyright allows the author to prevent.

Lawyer repellent (I hope): The quote comes from https://github.com/mongodb/docs/commit/50e48200cde7e2eaffdc6... , and anyone who receives this comment may copy it as they like.

There are some Go packages that can make config easy such as Viper or what I'll do in some of my quick/simple projects is to have a Config struct that I load from a JSON file. You can .gitignore the JSON file, and have your program on first startup write a default JSON file with some sensible default settings (like randomized secret keys for your cookies or JWT tokens and await only your database and email credentials to be filled in).

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;