alligotor
koanf
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
alligotor
-
A lightweight package for loading environment variables into structs
It's probably not a new idea but I still have to say I really like the package design and also how you designed the readme. I wrote a similar package a while back with the same thing in mind and it still works great for me. Maybe that's why I like yours 😅
-
Alligotor v0.2.0 - configuration package
If you're interested you can find usage examples at https://github.com/brumhard/alligotor or https://pkg.go.dev/github.com/brumhard/[email protected].
koanf
-
Nees help install knadh/koanf
LINK: https://github.com/knadh/koanf
-
App init and graceful watch lib recommendations ?
For configuration, I like Koanf.
-
Two ways to provide configuration: command-line, yaml file.
Of course. You should always use a good config package. caarlos0/env is okay but https://github.com/knadh/koanf is a better all around solution imo.
- Simplify Your Configurations in Go
-
Golang equivalent of Python’s click (CLT framework)
You can also use Viper with urfave/cli, or you can replace Viper with knadh/koanf, which I personally prefer.
-
Viper – Go Configuration with Fangs
Use viper with care. It has some dangerous fundamental flaws [1]. We got bitten hard, submitted a PR [2] and followed up for a year and a half to no avail, before I went ahead and reinvented the wheel and wrote koanf (plug), specifically to avoid viper's flaws.
Most importantly:
- Breaks JSON, YAML, TOML etc. language specs by forcibly lowercasing all keys internally. Dangerous because it can silently merge differently cased config keys into lowercase.
- Hard codes big unnecessary dependencies into the core, significantly bloating build sizes. No separation or abstraction.
[1] https://github.com/spf13/viper/pull/635
[2] https://github.com/knadh/koanf#alternative-to-viper
-
Extracting embedded files
It's not hard to a) look for a key in an environment variable b) accept a key as a parameter c) load a key from a file d) all of the above with something like koanf
- What are some good open source project to read when learning Go?
-
Coral, a friendly Cobra fork with nearly all its features, but only 4 dependencies
Came across this the other day https://github.com/knadh/koanf as an alternative to Viper.
-
What are your favorite packages to use?
https://github.com/knadh/koanf for config management. Readme contains why it's a good alternative to viper.
What are some alternatives?
env - 🔍 Load environment variables into a config struct
viper - Go configuration with fangs
env - A simple and zero-dependencies library to parse environment variables into structs
config - JSON or YAML configuration wrapper with convenient access methods.
dasel - Select, put and delete data from JSON, TOML, YAML, XML and CSV files with a single tool. Supports conversion between formats and can be used as a Go package.
konfig - Composable, observable and performant config handling for Go for the distributed processing era
go-toml - Go library for the TOML file format
cleanenv - ✨Clean and minimalistic environment configuration reader for Golang
isopod - An expressive DSL and framework for Kubernetes configuration without YAML
kelseyhightower/envconfig - Golang library for managing configuration data from environment variables
go-simple-config - open source for accessing and storing configuration
go-ini - Go package that encodes and decodes INI-files