ntfyx

ntfyx

Install the CLI.

Install ntfyx 0.1.0 with verified downloads and an atomic update.

macOS and Linux

Download the official installer, inspect it if desired, then run it. It detects your supported platform, verifies the release signature and checksum, and installs to ~/.local/bin by default. It needs curl and OpenSSL. If ntfyx is not on your PATH, run it by the full path below or add that directory using your usual shell configuration.

curl --fail --show-error --proto '=https' --tlsv1.2 https://ntfyx.me/install.sh -o ntfyx-install.sh
sh ntfyx-install.sh
"$HOME/.local/bin/ntfyx" version --json

Alternative: npm package from this site

The ntfyx package is not published to the npm registry. With Node.js 24 or later, install the exact package URL below using your existing npm installation scope and lifecycle policy. Its wrapper downloads and verifies the same signed standalone binary. If your policy disables lifecycle scripts, use the standalone installer; do not weaken that policy for this package.

npm install --global https://ntfyx.me/releases/0.1.0/ntfyx-0.1.0.tgz
ntfyx version --json

Connect

Start a five-minute pairing session and scan it in a compatible iPhone build. Confirm the Topic and Source on the phone. The iPhone app is awaiting App Store review. Only use the explicit staging origin when you intend to connect to the separate test environment.

ntfyx connect
ntfyx send "Build complete"
ntfyx ask "Deploy to staging?" --allow-deny
# Separate staging environment:
ntfyx connect --server https://api.staging.ntfyx.me

Updates and rollback

Standalone installs use ntfyx upgrade. The release signature and checksum are verified before an atomic replacement; failed downloads preserve the prior binary and credentials. Successful replacements retain a .rollback binary, and version downgrades are refused. npm installations remain owned by your package manager and do not self-replace.

ntfyx upgrade
ntfyx version --json

Manual downloads and verification

Choose the archive for your CPU and operating system. Both macOS builds are Developer ID signed and notarized. Linux requires glibc. Check the signed manifest and checksum before running a manually downloaded file.