Repository navigation
v1.2.0
This release is about packaging and documentation: the GUI binary is now a
single download that also carries the complete CLI, and the manual is published
as a website.
GUI and CLI binaries
- The GUI binary is now called
mhub-gui(previouslymhub-webgui) and is a
superset of the CLI: it dispatches the same commands, somhub-gui database initworks exactly likemhub database init. One download is enough to
manage MonitorHub from the command line or from a browser. - The Windows GUI ships as an onedir folder in a versioned zip
(mhub-gui-<version>-windows.zip) instead of a onefile executable. A onefile
build of the Streamlit application spends several seconds unpacking itself on
every start; the folder starts immediately. - The Linux GUI stays a single self-contained file.
build_project.pygained an--layout onefile|onediroption and anall
target. A failed build now stops immediately with an explanation instead of
continuing to the next target.
Continuous integration
- The GUI artifact is built and published by CI, alongside the CLI.
- Workflow actions were moved to Node 24 runtimes.
utils/check_actions.pyaudits the Node runtime every workflow action
declares, so an action that drops Node 24 support fails the build instead of
being force-migrated by GitHub.- A Dependabot configuration keeps the workflow actions current.
Documentation
- The manual is published with MkDocs Material to GitHub Pages:
https://transparent-systems.github.io/monitorhub/ - The build runs
mkdocs build --strict, so a link to a page that does not
exist fails the build rather than shipping a broken manual. - New pages cover installation, the first monitor, remote and command profiles,
the CLI, the database, placeholders and the architecture. - The README gained a table of contents and links to the published manual.