Yuneta Simplified is a development framework focused on messaging and
services, built on the
event-driven,
automata-based and
object-oriented
paradigms. Every component is a state machine, every message is JSON, and the
state machine is where things happen — so the trace of a running system is
its execution log.
It is a real-time system for Linux, with development, testing and deployment included. It collects data from devices, adapts protocols between systems, and publishes, subscribes and queries messages in real time, with historical storage on time-series, key-value, flat-file and graph stores. Messages travel encrypted or in plain text, and live on disk or only in transit.
Yuneta produces fully static binaries by default — no shared libraries, no dynamic linker. A compiled yuno is copied to any Linux machine of the same CPU architecture and runs there, with nothing to install. There are versions in C (the reference implementation) and JavaScript (browser and Node).
Start here¶
Dependencies, environment and a first build. Start here to get a working tree.
GClass, gobj, yuno, events. The four words the rest of the documentation is written in.
The engineering decisions behind the framework, and what each one buys and costs.
Running systems: the agent, the yuno lifecycle, traces, IPC, realms, auth and the treedb.
The full table of contents is in the left sidebar. The API reference is organized there by subsystem: GObj, Helpers, Logging, Parsers, Timeranger2, TLS, Event Loop and JavaScript.
Whole documents¶
Some things do not fit a chapter. These are single pages, each one written to be read from top to bottom.
Yuneta in one page: services, roles and messages without the runtime that usually pays for them, with a bill next to every decision.
The auth_bff exchange as a graph that runs, with the real gobjs and the real events on the edges. Five scenarios.
Not a diagram of the UI library, the library itself, in your browser. Open it on a phone too: the layouts change per breakpoint.
What the Back button must do in an application that is one page: history, overlays, and never losing the reader.
Why a package upgrade deletes a file it is supposed to keep, down to the
%posttrans that fixes it.
Then¶
Domain Model gives the vocabulary the framework uses to model reality — realms, entities, messages, CRUDLU. The Guides show how to build with it, and Inspiration is optional: the humanist angle that shaped the vocabulary.