see also: https://zookeeper.apache.org/
Show HN: Comfygure – A small CLI to manage application configurations
21–30 of 33 posts
Re: Show HN: Comfygure – A small CLI to manage application configurations
#22Hmm props to getting this out, but my way is has always been "bash is good enough" ja its not perfect a d feature rich but gets you 80% there and most linux based coders knows enough bash. I hate learning a new "language" just to deploy code or servers. Guess im just too old :)
Re: Show HN: Comfygure – A small CLI to manage application configurations
#23At my work, we use an internal config store developed by another team for app config management, versioning and audit history. It’s a bit flaky so we’ve been looking to replace it but don’t want to spend the company’s money building it. We’ve been looking but have not really found anything OSS. We’re looking for: - store text/binary documents - full audit history of document versions - get/put like api to retrieve/re…
Hashicorp Vault hits most (all?) of these points
Vault is for secret management. If you are just looking at a key value based store or a service discovery tool, you might want to have a look at consul by Hashicorp.
Re: Show HN: Comfygure – A small CLI to manage application configurations
#24Earlier quoted context omitted.
I think the argument isn't so much that "everyone needs to be able to push to production" as much as "more than one person should be able to push to production". Bus factor is an important variable.
That's like saying a company needs two CEOs because of bus factor. Somebody else can take over the role of being responsible for pushing to production any time.
When it’s a no-tools manual process? Unlikely.
Re: Show HN: Comfygure – A small CLI to manage application configurations
#25At my work, we use an internal config store developed by another team for app config management, versioning and audit history. It’s a bit flaky so we’ve been looking to replace it but don’t want to spend the company’s money building it. We’ve been looking but have not really found anything OSS. We’re looking for: - store text/binary documents - full audit history of document versions - get/put like api to retrieve/re…
Hmm, I’m actually working on a project that’s hopefully not too orthogonal to your need but could overlap on a couple of points above - https://www.deltatrail.io. Basically changelog as a service (which may cover the audit trail history you mention). Our logic is that most shops don’t want to build something like this from scratch. Take a look if you’d like. We are still in beta and experimenting with market so let me know if there is a potential overlap and we can fill in the gaps where needed. Reachable at Ryan at Deltatrail.io.
Re: Show HN: Comfygure – A small CLI to manage application configurations
#26Hmm props to getting this out, but my way is has always been "bash is good enough" ja its not perfect a d feature rich but gets you 80% there and most linux based coders knows enough bash. I hate learning a new "language" just to deploy code or servers. Guess im just too old :)
Thanks!
Bash is just fine, and if you don't need anything else to share configs with your team, it's totally fine :)
We built this tool because we had a need (everything is explained in the blog post)
Re: Show HN: Comfygure – A small CLI to manage application configurations
#27Does it have any features to handle inheritance / composition of configurations?
We usually have a slew of different environments that are mostly the same except for one or two parameters. I would like to find a solution that has the ability to control common parameters in one place without having to code the inheritance into every language / setting where the config is accessed.
In general it seems like simply storing your config in JSON or YAML and putting it in git provides most of the features of many config solutions and the overhead of deploying something separate to handle it rarely justifies the marginal benefit from that.
Re: Show HN: Comfygure – A small CLI to manage application configurations
#28Does it have any features to handle inheritance / composition of configurations? We usually have a slew of different environments that are mostly the same except for one or two parameters. I would like to find a solution that has the ability to control common parameters in one place without having to code the inheritance into every language / setting where the config is accessed. In general it seems like simply stori…
I didn't want to jump in with this earlier since comfy is the main topic here but https://configrd.io will do the inheritance you are asking about. It's not cli but also has an API, handles secrets and deploys on prem.
Re: Show HN: Comfygure – A small CLI to manage application configurations
#29Does it have any features to handle inheritance / composition of configurations? We usually have a slew of different environments that are mostly the same except for one or two parameters. I would like to find a solution that has the ability to control common parameters in one place without having to code the inheritance into every language / setting where the config is accessed. In general it seems like simply stori…
I didn't want to jump in with this earlier since comfy is the main topic here but https://configrd.io will do the inheritance you are asking about. It's not cli but also has an API, handles secrets and deploys on prem.
thanks! actually looks really cool, love the integrated support for storing encrypted secrets (even if not supporting many providers yet). Will explore it more.
Re: Show HN: Comfygure – A small CLI to manage application configurations
#30I just wish there was more of a standard for for configuration files. Aren't all config files at some level going to be tree like structures? I know it is impossible for everyone to agree on one format, like yaml vs json, vs xml etc. but maybe there could be a common library and standard that could allow each application to load it's configuration from any of these types of files? That way if one organization or distro or whatever wanted to all use Yaml (for example) for all of their config, they could do that.