Notes
First real update and public documentation
The first update from the panel, with a real rollback along the way.
2 min read
Release night: the installation and update chain has passed its first real test, and the project debuts its public documentation.
Clean package and installation from the signed catalog
The installation package now comes from git archive: the previous one was carrying __pycache__ and local metadata. The core is installed from the signed digests in the catalog and the version is recorded from the first boot. In the first full cleanup, fclean removed containers and volume but stopped when trying to delete a directory; after fixing the deletion, a new installation finished cleanly, without the previous test data. Verified: 47 API tests, current Alembic migration, active updater, and healthy public and administrative pages on desktop and mobile.
First real update: 0.1.8 → 0.1.9
The v0.1.9 release adds Web v… to the footer of the public image; the panel keeps the core version separately. From the panel, the administrator started the transition from 0.1.8 to 0.1.9: the work finished in done, API and panel healthy with signed digests and the previous public image intact.
Not everything worked on the first try: the public image check was connecting via localhost (IPv6) and the gateway was only listening on IPv4. The rollback restored the previous image without touching the DB or media; with the check pointing to 127.0.0.1, the retry installed the v0.1.9 digest. In fact, the rollback system tested itself, unintentionally.
Public wiki and logs, with the internal journal protected
Before publishing anything, the decision: wiki and development logs yes, raw internal journal no. It contains topology and private addresses; sensitive material is hidden with markers and the full bodies remain private. The wiki gathers 14 guides (installation, public web, panel, API, AI, operations, and two recipes for agents) and the logs export date, time, type, title, and a short excerpt, with sensitive identifiers masked. npm run check and npm run build pass, and 25 routes respond with 200 without overflows at 390 and 1440 px. A visual test detected excess width on the installation page on mobile; minmax(0, 1fr) and back to testing.
The product now installs, updates, and explains itself. Only the remote publication of the release is left.