run
A universal mechanism to manage goroutine lifecycles (by oklog)
koanf
Simple, extremely lightweight, extensible, configuration management library for Go. Support for JSON, TOML, YAML, env, command line, file, S3 etc. Alternative to viper. (by knadh)
run | koanf | |
---|---|---|
7 | 12 | |
1,466 | 2,385 | |
1.8% | - | |
4.5 | 7.6 | |
24 days ago | 1 day ago | |
Go | Go | |
Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
run
Posts with mentions or reviews of run.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-26.
-
App init and graceful watch lib recommendations ?
What I’ve done in the past is use a run group (like https://github.com/oklog/run ) and one of the goroutines in the group is just listening for a SIGINT/SIGTERM/etc. When it sees that it throws an error which cancels the root context and let’s each component handle its own graceful shutdown
-
Simple and flexible Go lifecycle manager library.
Just a bit of feedback. https://github.com/oklog/run is great and simple way of handling goroutines. It doesn't bake in signal handing, health checking, retries, because those are technically all separate concerns, that can be independently implemented. When I read your Readme, the lifecycle part immediately made me think of oklog/run.
-
How do i gracefully handle both a program interrupt, and goroutines finishing?
I would suggest to use this library https://github.com/oklog/run It is really helpful to manage goroutines lifecycles.
-
The Go way of combining multiple components in one application
https://github.com/oklog/run Sounds like you’re looking for something like this.
- Gracefully shutting down multiple servers in a single prorgam
-
Goshutdown: terminate your goroutines gracefully and in a timely manner
How does it compare to https://github.com/oklog/run?
-
Don't Panic: Catching Panics in Errgroup
There is an interesting discussion which has an alternative view that, with few exceptions, panics should crash your program. I'm ok with that in development and testing, but would rather sleep soundly at night.
koanf
Posts with mentions or reviews of koanf.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-26.
-
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.