Oh hey, Cockpit; I remember when this was started. It was the Red Hat desktop team's skunkworks project to make an actual good server UI after the last few attempts failed; I can't find any evidence of it, but I swear there was this ridiculous project to generate a "Linux API" by automatically combining every other API and adding prefixes and headers. That came down from management since "APIs" were the hotness.

The goal was to make in-roads on Windows Server-like deployments. "Cattle, not pets" was becoming uber-popular, but the thinking on the desktop team was that there was still a wide market for pets. People with toy servers, small businesses that just want a server inside their network, they all deserve UIs that don't require heavy sysadmin-ing.

I think it turned out quite nicely, and it seems it's still going!

Are you thinking of Augeas? That was a project inside RH to parse nearly every config found in /etc, and be able to view and modify them all from a standard API.

Was? It still is: https://augeas.net/

I wanted to parse INI files a few weeks back and briefly looked at Augeas... the augtool syntax was a little too nonsensical or verbose for me. Felt like I had to be an expert with the entire tool even though all I wanted was 3% of its functionality.

I looked a little harder and then found jc[1] which made parsing the ini file easy, and since I didn't need full CRUD support I threw my hands up and used that instead. I _would_ like to find a fast and easy way to convert json/yaml to simple INI file syntax at the command line, or do idempotent modifications to the INI files without writing a command where 99% of it is describing to jq or awk what an INI file looks like.

[1]: https://github.com/kellyjonbrazil/jc