Show HN: Comfygure – A small CLI to manage application configurations

I have the feeling that most developers these days suffer from too much tooling in every area. And would be 2 to 10 times more productive without it.<p>Most friends that I watch doing their deployment would be way more productive by simply using rsync for file changes and raw database queries when the DB needs a change.

At my work, we use an internal config store developed by another team for app config management, versioning and audit history.<p>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.<p>We’re looking for:<p>- store text&#x2F;binary documents<p>- full audit history of document versions<p>- get&#x2F;put like api to retrieve&#x2F;replace documents<p>- GUI to explore history&#x2F;documents<p>- easily deplorable on Windows (ideally without an app server)<p>Anyone got any (more) suggestions?

I just wish there was more of a standard for for configuration files. Aren&#x27;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&#x27;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.

Hmm props to getting this out, but my way is has always been &quot;bash is good enough&quot; 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 &quot;language&quot; just to deploy code or servers. Guess im just too old :)

Does it have any features to handle inheritance &#x2F; composition of configurations?<p>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 &#x2F; setting where the config is accessed.<p>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.

I love the really cute name!

see also: <a href="https:&#x2F;&#x2F;zookeeper.apache.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;zookeeper.apache.org&#x2F;</a>