docs: document both Termux APT channels
termux.md only described the canary suite while release_artifacts.py and the bundled-release workflow publish releases/termux/stable (suite hermes-stable) for tagged releases. Lead with stable, show how to opt into canary, and name the channels in the README instead of a bare "prerelease".
This commit is contained in:
@@ -56,7 +56,7 @@ for Windows archive in Hermes' tool store. It does not replace your system Git.
|
||||
See [installation methods](https://hermes-agent.nousresearch.com/docs/getting-started/installation)
|
||||
for the separate MSIX/App Installer package and its update ownership.
|
||||
|
||||
> **Android / Termux:** A prerelease APT package is available for aarch64 devices. It includes Python, Node.js, and the TUI. Use the [Termux guide](https://hermes-agent.nousresearch.com/docs/getting-started/termux), not the desktop/server installer script.
|
||||
> **Android / Termux:** A signed APT repository is available for aarch64 devices, with a `stable` channel (tagged releases) and a prerelease `canary` channel. The package includes Python, Node.js, and the TUI. Use the [Termux guide](https://hermes-agent.nousresearch.com/docs/getting-started/termux), not the desktop/server installer script.
|
||||
>
|
||||
> **Windows:** Native Windows is fully supported — the PowerShell one-liner above installs everything. If you'd rather use WSL2, the Linux command works there too. Native Windows install lives under `%LOCALAPPDATA%\hermes`; WSL2 installs under `~/.hermes` as on Linux.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user