Workstation Deployment
Status: Available.
msh local runs as a local daemon on the operator's machine. A single install gets the desktop app, daemon, and CLI bundled together.
Install (macOS)
A native macOS app with a visual policy editor, approval banners, and audit log viewer. The cask bundles the daemon and CLI — one command installs everything.
Homebrew:
brew install --cask leonardaustin/tap/mezite-desktopDMG download — grab the latest release fromGitHub Releasesand drag Mezite Desktop to Applications.
The desktop app manages the daemon lifecycle. Launch the app and it starts the daemon automatically.
Install (Linux)
Linux (.AppImage): download fromGitHub Releases.
First-run setup
# Install the daemon service (launchd / systemd)
msh local install
# Verify the daemon is running
msh local status
# Run diagnostics
msh local doctorStarting / stopping the gateway
# Run the daemon in the foreground (debugging — `msh local install`
# registers it as a service for normal use)
msh local daemon
# Check status
msh local status
msh local installregisters a launchd (macOS) or systemd (Linux) service so the daemon starts automatically at login. Usemsh local uninstallto remove it.
Updating
msh local upgrade # download and apply the latest release
msh local upgrade --check # just check whether a newer release exists
# Or drive the daemon's self-update state machine directly:
msh local update check # force an immediate check against GitHub Releases
msh local update status # show the current update state
msh local update apply # apply the currently-staged update and restartPolicy file location
The policy YAML is at ~/.mezite/local/policy.yaml on both platforms. Edit it in the desktop app's built-in editor or in any text editor — the daemon hot-reloads it automatically.
See Policy Configuration for the full schema.
Managed workstations
Enrol this workstation with MezHub for centrally managed policy and audit upload. See Managed Policy. Managed policy fully replaces the local policy. After its first successful sync, an enrolled workstation keeps enforcing its cached managed policy during an outage. Before that first sync, its frozen local policy remains in effect.