Repository navigation
SidePulse.NET 0.1.0-beta.2
Pre-releaseSidePulse.NET 0.1.0-beta.2
Single-file portable executables with per-user installation and optional user PATH setup.
- Each runtime archive contains one self-contained executable plus its small
format-2 update manifest. Docs, dependency/runtime licenses and notices are embedded.
A copied executable works alone; native runtime libraries can use a per-user cache. spn install --dry-run,spn install,spn install --statusand the interactive
Settings → Installation screen provide a permanent per-user location without elevation.--add-to-pathchanges only user PATH on Windows. Unix uses a managed user-bin
launcher and, when needed, one explicit backed-up Bash/Zsh/sh profile block.
Command-name conflicts are refused. Repeated installation is idempotent.- New hook and detached-host setup use the stable installed executable. Existing
hook files still require explicit uninstall/reinstall; manual edits are preserved. - Verified upgrade, startup probe and rollback support the bundle layout.
Uninstall removes owned binaries/PATH entries while keeping credentials, settings,
user-added files and profile backups. Installed-process removal uses a waiting helper.
Install or upgrade
Download the matching Windows/Linux/macOS x64 or ARM64 archive and verify
SHA256SUMS. Extract and run .\spn.exe install --dry-run (PowerShell) or
./spn install --dry-run (Unix). Apply with install, optionally adding
--add-to-path; Unix supports --shell bash, zsh or sh.
The absolute installed executable works immediately; reopen terminals after PATH setup.
Beta 1's updater does not understand format 2. For that one transition, stop the
host, download the new executable, and use its installer or a separate permanent
directory. Existing owned/verified installations can be upgraded with backups;
unowned destinations and edited files are refused. Alpha's command rename still
requires the manual integration transition recorded in beta 1's notes.
Use spn docs --offline for full installation, PATH ownership and recovery details.
Hardware/firmware and installed-provider acceptance remain separate from native
CI. Other architectures are cross-built, and packages remain unsigned. Full saved
UI preferences and automatic migration of edited integrations remain open.
This candidate remains an unpublished draft until acceptance is reviewed.