TUI for yunetas
This is the TUI (Terminal User Interface) for Yuneta Simplified
Yuneta Simplified is a development framework about messages and services, based on Event-driven, Automata-based and Object-oriented programming.
Yuneta is based in functions, but it manages a system of virtual classes defined by programmatically and schematically.
All his philosophy is based on that virtual classes (namely GClass or class G).
All architecture done by configuration, based in schema, easy to see by human eye. Of course, you have an API functions to change configuration and data in real time.
For Linux and RTOS/ESP32.
Versions in C, Javascript and (TODO) Python.
For more details, see doc.yuneta.io
Commands
yunetas init # create build dirs, compiler/build-type from .config (menuconfig)
yunetas build # make install: SDK + registered projects
yunetas clean # make clean: SDK + registered projects
yunetas test # ctest
# External projects (registry in ~/.yuneta/projects.json, machine-local)
yunetas register-project <path> # <path> must contain yunos/CMakeLists.txt
yunetas unregister-project <name>
yunetas list-projects
yunetas init|build|clean <name>... # only those projects (SDK skipped)
yunetas init|build|clean --sdk-only # only the SDK
# Deploy helpers (wrappers over $YUNETAS_BASE/tools/agent/sync_*.py)
yunetas sync [-n|-a|...] # binaries AND configs together (recommended)
yunetas sync-binaries [-n|-a|...] # outputs/yunos vs the local agent
yunetas sync-configs [-n|-a|-r|...] # auto-match batches/<host>/ to the agent's realm_ids
yunetas sync-configs --host <host> [...] # or target one batches dir explicitly
yunetas upgrade-yunos [--no-snap|--snap-name N|-y|-n] # find-new-yunos -> snapshot -> deactivate-snap
On a runtime-only node (installed from the .deb/.rpm: outputs/,
outputs_ext/, tools/ and .config, but no framework sources and no
YUNETA_VERSION) there is no SDK to build, so init/build/clean with no
arguments process the registered projects only — naming them is optional.
--sdk-only is an error there.
Deploy flow
Two steps: push the artifacts, then promote them.
# 1. Push binaries AND configs in one go (so a binary bump never ships
# without its matching config bump — the verify-by-default footgun:
# a new fail-closed runtime against a stale no-CA config breaks OIDC).
yunetas sync # = sync-binaries + sync-configs
# 2. Promote the freshly installed releases to primary and restart.
yunetas upgrade-yunos # find-new-yunos (confirm) -> snapshot -> deactivate-snap
sync does not restart anything by itself; upgrade-yunos is the promote
step. It previews find-new-yunos first and stops there when there is
nothing new, then asks, then shoots a rollback snapshot (idempotent by name;
reuses an already-active snap instead of stacking a new one; --no-snap to
skip), then runs create=1, then deactivate-snap triggers
restart_nodes() on the agent. Preview the steps with -n.
A row that the agent marks already registered, pending promotion (deactivate-snap): create-yuno ... (a create=1 of an earlier run that was
never promoted, SDK 7.25.5 and later) is counted apart. It needs no
create=1, only the promotion:
1 new yuno row(s) would be created:
create-yuno id=gate^one ...
1 yuno row(s) already registered, pending promotion:
already registered, pending promotion (deactivate-snap): create-yuno id=gate^two ...
...
1 created, 1 already registered.
When every row is already registered, create=1 is skipped and the command
goes on to deactivate-snap.
For a same-version hot-patch (no APP_VERSION bump) you don't need
upgrade-yunos: sync then bounce the affected yunos (kill-yuno +
run-yuno / play-yuno).
How build this package
Install pdm
This package use pdm to build and publish.
pip install pdm
pip install cement
pip install plumbum
pip install fastapi
pip install "uvicorn[standard]"
pip install "typer[all]"
Build and publish
# Firstly change the version (explained below)
# Next go to source root folder
pdm build
pdm publish --username __token__ --password <your-api-token> # (me: the full command is saved in publish-tui_yunetas.sh)
Tests
The tests use unittest and need the packages of the CLI (typer, rich), so
run them with the Python where the CLI is installed:
python -m unittest discover -s tests
Install the package in editable mode using pip from the source root folder:
pip install -e .
Change the version
Edit the
__version__.pyfile and change the variable__version__. Then build and publish
1 maintainer
Metadata
1 maintainer
Release files for yunetas 0.20.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| yunetas-0.20.4.tar.gz | 54.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| yunetas-0.20.4-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 110.5 kB
Release files / yunetas-0.20.4.tar.gz
| Download URL | yunetas-0.20.4.tar.gz |
|---|---|
| Size | 54.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
469c48ede62472d812c2476cb7f49a3c866377d056913e10344f8e67ef21661f
|
|
BLAKE2b-256 checksum How to use checksums |
1e55ab55269b7d1eda661c776316f12cbcab39499455037dfea458f87ca452df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.29.2 CPython/3.14.4 Linux/7.0.0-38-generic
|
Release files / yunetas-0.20.4-py3-none-any.whl
| Download URL | yunetas-0.20.4-py3-none-any.whl |
|---|---|
| Size | 55.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dc576b3f4e71fc1fe6b13ebdac570a6aa8701f90ec159be54e3b1798fdff1c11
|
|
BLAKE2b-256 checksum How to use checksums |
41b0491648cea35c499c117d3b21ec48b18b483b1eec930a9d2316d1b9e16fde
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.29.2 CPython/3.14.4 Linux/7.0.0-38-generic
|
Security for yunetas 0.20.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
