scripts: add curl|sh installer for the daemon CLI#17
Merged
Conversation
The release artefacts are bare tarballs — extracting them dropped `myownmesh` in CWD, not on PATH, so the "preb-built daemon" path left users without a working CLI. Add scripts/install.sh and scripts/install.ps1 that detect the platform, fetch the matching release asset, verify the SHA-256 sidecar, install to /usr/local/bin (or ~/.local/bin / %LOCALAPPDATA%\Programs\MyOwnMesh as fallback), and append the prefix to PATH if it isn't there yet. Falls back to `cargo build --release --bin myownmesh` from a shallow clone if the release lookup fails. Lift the install snippet to its own top-level section in the README and replace the five hardcoded platform-suffix examples with the one-liner.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
myownmeshin CWD, not on PATH, so the "pre-built daemon" path left users without a working CLI on first install.scripts/install.sh(POSIX) andscripts/install.ps1that detect platform → fetch the matching release asset → verify the SHA-256 sidecar → install to/usr/local/bin(or~/.local/bin/%LOCALAPPDATA%\Programs\MyOwnMeshas fallback) → append the prefix to PATH if it isn't there yet.cargo build --release --bin myownmeshfrom a shallow clone if the release lookup fails or--from-sourceis passed.## Installsection in the README and replaces the five hardcoded platform-suffix examples with the one-liner. Renumbers the "Get started" subsections.Mirrors the MyOwnLLM installer pattern (
scripts/install.sh/install.ps1) so the muscle-memory carries over for users who already run both apps. Simpler than MyOwnLLM's — no Tauri runtime deps, no onnxruntime sideload.Test plan
sh -n scripts/install.sh— POSIX syntax check (passes locally under/bin/sh).MYOWNMESH_PREFIX=/tmp/x sh scripts/install.sh --dry-run— dry-run resolves prefix, looks up the release, logs the actions it would take without writing.curl -fsSL https://raw.githubusercontent.com/mrjeeves/MyOwnMesh/main/scripts/install.sh | sh→myownmesh serveworks in a new shell.irm …/install.ps1 | iex→ new terminal →myownmesh serveworks../scripts/install.sh --from-sourcefrom inside a fresh checkout uses the local tree (no clone) and installs the built binary.Generated by Claude Code