store alternatives and similar packages
Based on the "Configuration" category
-
kelseyhightower/envconfig
Go library for managing configuration data from environment variables. -
konfig
Composable, observable and performant config handling for Go for the distributed processing era. -
hjson
Human JSON, a configuration file format for humans. Relaxed syntax, fewer mistakes, more comments. -
joshbetz/config
A small configuration library for Go that parses environment variables, JSON files, and reloads automatically on SIGHUP. -
gookit/config
application config manage(load,get,set). support JSON, YAML, TOML, INI, HCL. multi file load, data override merge. -
koanf
Light weight, extensible library for reading config in Go applications. Built in support for JSON, TOML, YAML, env, command line. -
gcfg
read INI-style configuration files into Go structs; supports user-defined types and subsections -
goConfig
Parse a struct as input and populates the fields of this struct with parameters fom command line, environment variables and configuration file. -
harvester
Harvester, a easy to use static and dynamic configuration package supportig seeding, env vars and Consul integration. -
onion
Layer based configuration for Go, Supports JSON, TOML, YAML, properties, etcd, env, and encryption using PGP. -
configure
Provides configuration through multiple sources, including JSON, flags and environment variables. -
sprbox
Build-environment aware toolbox factory and agnostic config parser (YAML, TOML, JSON and Environment vars). -
gone/jconf
Modular JSON configuration. Keep you config structs along the code they configure and delegate parsing to submodules without sacrificing full config serialization.
Do you think we are missing an alternative of store or a related project?
Popular Comparisons
|
SaaSHub - Software Alternatives and Reviews
View more from us
|
README
Store
Store is a dead simple configuration manager for Go applications.
I didn't like existing configuration management solutions like globalconf, tachyon or viper. First two just don't feel right and viper, imo, a little overcomplicated—definitely offering too much for small things. Store supports either JSON, TOML or YAML out-of-the-box and lets you register practically any other configuration format. It persists all of your configurations in either $XDG_CONFIG_HOME or $HOME on Linux and in %APPDATA% on Windows.
Look, when I say it's dead simple, I actually mean it:
package main
import (
"log"
"time"
"github.com/tucnak/store"
)
func init() {
// You must init store with some truly unique path first!
store.Init("cats-n-dogs/project-hotel")
}
type Cat struct {
Name string `toml:"naym"`
Clever bool `toml:"ayy"`
}
type Hotel struct {
Name string
Cats []Cat `toml:"guests"`
Opens *time.Time
Closes *time.Time
}
func main() {
var hotel Hotel
if err := store.Load("hotel.toml", &hotel); err != nil {
log.Println("failed to load the cat hotel:", err)
return
}
// ...
if err := store.Save("hotel.toml", &hotel); err != nil {
log.Println("failed to save the cat hotel:", err)
return
}
}
Store supports any other formats via the handy registration system: register the format once and you'd be able to Load and Save files in it afterwards:
store.Register("ini", ini.Marshal, ini.Unmarshal)
err := store.Load("configuration.ini", &object)
// ...