# Manual CLI Installation¶

Last updated for CLI release v1.4.0.

The newest binary releases can be found here. With the exception of the .exe and .dmg files, they are archives of the latest executable binaries for each release. Although most of this will be extract and go, instructions are provided for Windows, macOS, and Linux below.

Windows instructions (click to expand)

Note

Windows 7/8/10 provides native support for .zip files, therefore it is preferable to use the .zip file. If you decide to download the .tar.gz file, it will need to be extracted using a third-party application (7-Zip, WinRAR, etc.). Instructions are provided for the .zip file.

Architecture Filename
32-bit bitum-windows-386-v1.4.0.zip
64-bit bitum-windows-amd64-v1.4.0.zip
2. Navigate to download location and extract the .zip file:

Right click on the .zip file, select “Extract All…” and a prompt should open asking for the directory to use. The default will extract the .zip to a folder with the same name. It should include bitumctl, bitumd, bitumwallet, sample-bitumctl.conf, sample-bitumd.conf, and sample-bitumwallet.conf.

macOS instructions (click to expand)

Architecture Filename
64-bit bitum-darwin-amd64-v1.4.0.tar.gz
2. Navigate to download location and extract the .tar.gz file:

Finder: simply double click on the .tar.gz file.

Terminal: use the tar -xvzf filename.tar.gz command.

Both of these should extract the .tar.gz file into a folder that shares the same name. (e.g. tar -xvzf bitum-darwin-amd64-v1.4.0.tar.gz should extract to bitum-darwin-amd64-v1.4.0). It should include bitumctl, bitumd, bitumwallet, sample-bitumctl.conf, sample-bitumd.conf, and sample-bitumwallet.conf.

Note

If you are using Safari on macOS Sierra and have the ‘Open “safe” files after downloading’ preference enabled, .gz and .zip files are automatically extracted after download. The tar -xvzf filename.tar.gz command results in this error: tar: Error opening archive: Failed to open 'filename.tar.gz'. Use tar -xvzf filename.tar instead (remove the .gz from the previous command).

Linux instructions (click to expand)

Architecture Filename
32-bit bitum-linux-386-v1.4.0.tar.gz
64-bit bitum-linux-amd64-v1.4.0.tar.gz
32-bit ARM bitum-linux-arm-v1.4.0.tar.gz
64-bit ARM bitum-linux-arm64-v1.4.0.tar.gz
2. Navigate to download location and extract the .tar.gz file:

Ubuntu File Browser: simply right click on the .tar.gz file and select “Extract Here”.

Terminal: use the tar -xvzf filename.tar.gz command.

Both of these should extract the .tar.gz file into a folder that shares the same name. (e.g. tar -xvzf bitum-linux-amd64-v1.4.0.tar.gz should extract to bitum-linux-amd64-v1.4.0). It should include bitumctl, bitumd, bitumwallet, sample-bitumctl.conf, sample-bitumd.conf, and sample-bitumwallet.conf.

## Minimum Configuration¶

At the very minimum, for bitumd, bitumwallet, and bitumctl to be able to communicate with each other, they need to be launched with the same rpcuser/rpcpass combination. For manual configuration please follow these steps:

1. If the OS-specific home directories listed in Configuration File Locations do not exist, please create them for bitumd, bitumwallet, and bitumctl.

2. Choose an arbitrary username and password, these will only be used for each application to communicate via remote procedure call. The easiest configuration is to set them all equal.

3. Using your favorite text editor, create a new text file and add the following lines:

[Application Options]


Save it as bitumd.conf in bitumd‘s home directory.

4. Create another new text file and add the following lines:

[Application Options]


Save it as bitumwallet.conf in bitumwallet‘s home directory.

5. Create a third text file and add the following lines:

[Application Options]

Save it as bitumctl.conf in bitumctl‘s home directory.
All command line options can be put in the config file. The sample config files in the release package give additional options or you can run one of the programs with the -h flag to show a list and description of all options for the specified application.