Skip to main content
fyrer is distributed as a single self-contained binary compiled from Rust — there are no runtimes, daemons, or additional dependencies to manage. There are five ways to get it onto your machine. Pick whichever suits your platform and workflow.
Prerequisites: curl, uname, and sha256sum (or shasum) on Linux or macOS.
The script detects your OS and architecture, downloads the matching prebuilt binary from the latest GitHub release, verifies its SHA-256 checksum, and installs it to ~/.local/bin (or $XDG_BIN_HOME if set).
Override the install location with FYRER_INSTALL_DIR, or pin a specific version with sh install.sh v0.3.3. If the install directory isn’t already on your PATH, the script prints the export PATH=... line to add to your shell profile.

Verify installation

Confirm that fyrer is on your PATH and check the installed version:
You should see output like fyrer 0.3.3. If the command is not found, make sure your install directory is on your PATH:
  • ~/.local/bin for the Unix install script
  • %LOCALAPPDATA%\fyrer\bin for the Windows install script
  • your npm global bin directory for npm installs
  • ~/.cargo/bin for cargo install and source builds
fyrer looks for fyrer.yml in the current working directory by default. Always run fyrer from the directory that contains your config file. If you need to point at a config in a different location, pass the --config flag: