@kisuke/cli
v1.2.30
Published
Lifecycle-free bootstrapper for the Kisuke CLI runtime
Readme
@kisuke/cli
Lifecycle-free bootstrapper for the Kisuke CLI. Installing this package does not
download a runtime, start a daemon, or register a service. The first kisuke
invocation verifies and installs the matching signed runtime beneath the
flavor-aware Kisuke home directory, then runs it with the original arguments and
stdio.
npm install -g @kisuke/cli
kisukeRuntime files live in ~/.kisuke/runtime for production,
~/.kisuke-staging/runtime for staging, or beneath KISUKE_HOME when set. npm
uninstall intentionally leaves shared runtime and user data intact; use
kisuke uninstall to remove the runtime while preserving user data.
Supported overrides:
KISUKE_HOME: absolute Kisuke home directory.KISUKE_RUNTIME_PATH: absolute path to an already prepared bundle.KISUKE_VERSION: exact runtime version for this invocation.KISUKE_DOWNLOAD_URL: HTTPS origin, or loopback HTTP for tests.KISUKE_NO_PROGRESS=1: disable download progress.KISUKE_LAUNCHER_PATH: installed launcher used for daemon restoration after activation.HTTPS_PROXY,HTTP_PROXY, andNO_PROXY: download proxy configuration.
The package contains no third-party runtime dependencies and no npm lifecycle
scripts. Release workflows must replace manifestPublicKeyBase64 in
config.json with the base64-encoded trusted RSA public-key PEM used to sign the exact bytes of every
manifest.json.
See docs/runtime-installer.md for the full
resolution, verification, activation, update, rollback, release, and removal
design.
Runtime manager
runtime-manager.mjs is also an executable helper for the bundled CLI and the
native installer:
runtime-manager.mjs resolve [--version VERSION]
runtime-manager.mjs launch [--package-version VERSION] [--legacy-root DIR] -- [CLI_ARGS...]
runtime-manager.mjs install [--version VERSION] [--no-activate] [--prune]
runtime-manager.mjs install-launcher [--no-modify-path]
runtime-manager.mjs activate --version VERSION
runtime-manager.mjs prune
runtime-manager.mjs removeinstall additionally accepts --manifest, --signature, and --archive for
a native stage-zero installer that has already downloaded those files.
