Installing the Command–Line Interface (CLI)

Open the Terminal app.

Unzip the file.

If you are using macOS 10.15 Catalina release (or later), you need to add the Flywheel CLI as a security exception. If you are using an earlier macOS version or Linux, continue to step 4. 

To add the Flywheel CLI as a security exception:

1. Right-click on fw, and click Open.
   
   
2. Click Open on the warning prompt.
   
   

In Terminal, navigate to the Flywheel CLI. For example:

OS X

cd ~/Downloads/darwin_amd64*

Linux

cd ~/Downloads/fw-linux_amd64/linux_amd64*

(Optional) To make it easier to access the Flywheel CLI later on, you can add it to your PATH (If you want to learn more about the PATH variable, see this article by Oracle ). You don't need to add the Flywheel CLI to your PATH. However, if you do not add it, you must either enter the file path where fw resides each time your enter a command or you must run the commands from the same folder as fw.

To add the Flywheel CLI, enter the following command:

sudo mv ./fw /usr/local/bin

Double-click fw-windows_amd64<version_number> to unzip the file. You should see a fw.exe file inside. This is the Flywheel CLI. 

Open the Command Prompt utility as an administrator.

In the Command Prompt, navigate to fw-windows_amd64<version_number>.

For example:

cd C:\Users\[username]\Downloads\windows_amd64*

(Optional) To make it easier to access the Flywheel CLI later on, you can add it to your PATH (If you want to learn more about the PATH variable, see this article by Oracle ). You don't need to add the Flywheel CLI to your PATH. However, if you do not add it, you must either enter the file path where fw.exe resides each time your enter a command or you must run the commands from the same folder as fw.exe.

Enter the following command to add the Flywheel CLI to you PATH:

setx path "%path%;C:\your_path"

For example:

setx path "%path%;C:\Programs\fw.exe"