UNI(8)

🦋 UNI(8) 🦋

okay bestie, welcome to uni(8) from the System Manager's Manual — this is the little tool that lets you talk directly to UniConf from your shell, and honestly? it's giving main character energy 💅

---

✨ NAME ✨

uni — a program to interface with the UniConf configuration system 🌸

---

✨ SYNOPSIS ✨

uni get KEY [DEFAULT]

uni set KEY [VALUE]
uni xset KEY [VALUE]

uni keys KEY
uni hkeys KEY
uni xkeys KEY

uni dump KEY
uni hdump KEY
uni xdump KEY

---

✨ DESCRIPTION ✨

So UniConf is the One True Configuration system that includes all the others, because it has plugin backends and frontends. Or, if we're being less grandiosely dramatic about it: it's a lightweight, distributed, cacheable tree of strings. 🌳✨

uni is what you use to interface directly with the UniConf system. Its primary use is for diagnostic purposes, but it can also be used to add UniConf support to shell scripts. iykyk 🫶

---

✨ ENVIRONMENT VARIABLE ✨

• UNICONF — before using uni, you must tell it which UniConf moniker you wish to query, and you do that by setting this environment variable. no pressure bestie but it literally will not know where to look 🙈

Monikers are used to contact UniConf back-ends, be they a uniconfd server, or a local file. For example, they could be:

• a filename (ini:/var/lib/app/config.ini), or
• a network address, (tcp:open.nit.ca:4111).

---

✨ COMMANDS ✨

• get — retrieve the VALUE associated with the provided KEY within the UniConf database. If a DEFAULT is provided, this will be returned if the KEY has no associated VALUE. 🎀
• set — assign the provided VALUE to the provided KEY. Heads up though: UniConf provides no guarantee that the entry is committed throughout the database. The next get command for this KEY may not return the most recently set value, due to caching, or the existence of a read-only generator. 💀
• xset — assign, to the provided KEY, the contents of the standard-input stream. Use this command to pipe information into the UniConf database. 🍓
• keys — list all the sub-keys contained within the provided KEY.
• hkeys — list all the sub-keys, recursively, contained within the provided KEY. Since any KEY may contain sub-keys, UniConf provides no guarantee that there are no circular references. 🌀
• xkeys — list all the sub-keys contained within the provided KEY, which can contain wildcards. See the WILDCARDS section. ✨
• dump — list all the sub-keys and their values, contained within the provided KEY.
• hdump — list all the sub-keys and their values, recursively, contained within the provided KEY.
• xdump — list all the sub-keys and their values, contained within the provided KEY, which can contain wildcards.

---

✨ WILDCARDS ✨

A KEY looks just like a normal slash-delimited path. The root of the UniConf tree has a KEY named /. Sub-keys can be accessed by names such as /software/myapp/version. 🌈

With wildcards, you can access more than one key at a time. obsessed.

• * — to access a sub-key within any one level of keys, use the asterisk like so: /software/*/version. This retrieves all keys of version that are one level beneath /software. ⭐
• ... — to access a sub-key anywhere beneath a key, use the ellipsis like so: /.../version. This retrieves all keys of version that are zero or more levels beneath the root (i.e. any appearance of version within the database). 👑

---

✨ SEE ALSO ✨

• uniconfd(8)

---

✨ AUTHORS ✨

This software was written by the hackers at Net Integration Technologies. Contact us at <wvstreams-dev@lists.nit.ca> 💜

---

and that's the whole page bestie, we ate and left no crumbs 🧚✨ this was Uni 4.2.2, dated September 2004 — yeah, she's vintage, but she still slays 💖🎀🌸

UNI(8)