Skip to main content
You can use voiceflow-cli by installing a pre-compiled binary (in several ways), using Docker, or compiling it from source. In the below sections, you can find the steps for each approach.

Install a pre-compiled binary

homebrew tap

Install the Voiceflow CLI:

snapcraft

aur

scoop

chocolatey

apt

yum

nix

nixpkgs

!!! info
The package in nixpkgs might be slightly outdated, as it is not updated automatically. Use our NUR to always get the latest updates.

nur

First, you’ll need to add our NUR to your nix configuration.
You can follow the guides here.
Once you do that, you can install the packages.

deb, rpm and apk packages

Download the .deb, .rpm or .apk packages from the [OSS releases page][releases] and install them with the appropriate tools.

go install

bash script

Additional Options

You can also set the VERSION variable to specify
a version instead of using latest.
You can also pass flags and args to voiceflow-cli:
!!! tip
This script does not install anything, it just downloads, verifies and runs voiceflow-cli. Its purpose is to be used within scripts and CIs.

manually

Download the pre-compiled binaries from the [releases page][releases] and copy them to the desired location.

Verifying the artifacts

binaries

All artifacts are checksummed, and the checksum file is signed with [cosign][].
  1. Download the files you want along with the checksums.txt, checksum.txt.pem, and checksums.txt.sig files from the [releases][releases] page:
  2. Verify the signature:
  3. If the signature is valid, you can then verify the SHA256 sums match with the downloaded binary:

docker images

Our Docker images are signed with [cosign][]. Verify the signatures:
!!! info
The .pem and .sig files are the image name:tag, replacing / and : with -.

Running with Docker

You can also use voiceflow-cli within a Docker container.
To do that, you’ll need to execute something more-or-less like the examples below.
Registries: Example usage:
Note that the image will almost always have the last stable Go version. If you need other packages and dependencies, you are encouraged to keep your own image.

Compiling from source

If you just want to build from source for whatever reason, follow these steps: clone:
get the dependencies:
build:
verify that it works: