Meltemi
Pick your platform
| Platform | Core (daemon + terminal) | Desktop client |
|---|---|---|
| Windows 10 1809+ / 11 | meltemi-Windows.zip | meltemi-desktop-Windows.msi |
| macOS 13+ | meltemi-macOS.tar.gz | meltemi-desktop-macOS.dmg |
| Linux (Debian/Ubuntu) | meltemi-Linux.tar.gz | meltemi-desktop-Linux.deb |
The core archive carries both binaries: the daemon meltemid
and the terminal client meltemi. No desktop installer embeds a
browser: each one uses your operating system's own web view — bootstrapped
on Windows, already there on macOS, declared as a package dependency on
Linux. That is why there is no AppImage: the format is self-contained by
construction, so it would have to carry the engine, about 79 MB of it.
Outside the Debian family there is no desktop installer yet. The terminal
client and the daemon run on any distribution from the core archive, and
the desktop app builds from source. An .rpm is the next step.
Or use the install script
The scripts are short and meant to be read before they are run. Each one is
published as a release asset with its checksum inside the signed
SHA256SUMS, and each verifies the archive's checksum and
refuses on a mismatch. There is no blind pipe into a shell here:
download it, read it, then run it.
macOS and Linux
curl -fsSLO https://github.com/askenaz-dev/meltemi/releases/latest/download/install.sh
less install.sh
sh install.shWindows
irm -OutFile install.ps1 https://github.com/askenaz-dev/meltemi/releases/latest/download/install.ps1
notepad install.ps1
./install.ps1
Both place meltemi and meltemid on your path and
create the short alias mel. Prefer to do it by hand? The
manual equivalent is written at the top of each script.
Verify what you downloaded
Every release publishes a SHA256SUMS with a detached
signature made with the maintainer's key, plus a build attestation minted
by the release workflow itself. Three checks, ordered by what each one
buys: the checksum tells you the file arrived intact, the signature tells
you the maintainer vouched for it, and the attestation tells you which
repository, commit and workflow produced it. The commands — and what each
check can and cannot prove — are in the release documentation.
SHA256SUMS of the latest release Checksum, signature and provenance procedure
Or build it from source
One toolchain, pinned in the repository, and no code generation step. The repository's own quickstart carries the exact commands, the platform prerequisites for the desktop client, and how to run the whole test suite.