-
Notifications
You must be signed in to change notification settings - Fork 68
Open
Description
We want a low-friction install path for end users:
curl -fsSL https://dexto.ai/install | bashinstalls a standalonedextoexecutable (no separate Bun/Node prerequisite).- Keep existing npm-based install working in parallel.
Motivation
The repo is migrating to Bun for tooling/runtime, but requiring users to separately install Bun adds friction. A standalone executable + a curl install script avoids that and provides a predictable install/upgrade story.
Proposed approach
- Produce standalone binaries for macOS (arm64/x64), Linux (x64/arm64; consider musl/baseline variants), Windows (x64).
- Prefer compiling with Bun (
Bun.build({ compile: ... })) to bundle the runtime.
- Prefer compiling with Bun (
- Release workflow (GitHub Actions) builds artifacts and uploads them to GitHub Releases with consistent filenames.
- Install endpoint
https://dexto.ai/installserves a small shell script that:- detects OS/arch
- downloads the correct artifact for latest (or a specified version) from GitHub Releases
- installs into an XDG-friendly bin dir (e.g.
$XDG_BIN_DIR,$HOME/bin, or$HOME/.dexto/bin) - optionally updates shell PATH
- Optional hardening: checksums/signatures, retry logic, proxy support.
Open questions / decisions
- Where does the install script live/serve from? (dexto.ai infra vs GitHub Pages/proxying raw GitHub content)
- Do we also want an npm “wrapper” package that downloads/execs the correct platform binary?
- Version channels (stable vs dev/nightly) and how they map to releases/tags.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels