Installing & Running a Production Linux Node

The x64 installers are available from the downloads page. This requires the .NET Core 3.1 runtime to be installed. Installation will fail a dependency check otherwise.

Debian Package

curl -o runly.deb -L https://repo.runly.io/deb/runly_0.9.16_amd64.deb
sudo dpkg -i runly.deb

You can make sure you have the latest version by running:

sudo apt-get update && sudo apt-get upgrade

RPM Package

curl -o runly.rpm -L https://repo.runly.io/rpm/runly-0.9.16-1.x86_64.rpm
sudo rpm -ivh runly.rpm

You can make sure you have the latest version by running:

sudo yum update

Pacman Package

curl https://repo.runly.io/pacman/runlyrepo_pub.bin.gpg -o runly.gpg
sudo pacman-key --add runly.gpg
sudo pacman-key --lsign-key 984BD100502ED2A67117217AAFBBE45D951990D2
sudo echo "[runly]
Server = https://repo.runly.io/pacman/" >> /etc/pacman.conf
sudo pacman -Sy
sudo pacman -S runly

Binaries

The Linux binaries are self contained single file executables which are available from the downloads page. They do not require the dotnet core runtime to be installed. The following is an example of downloading and setting the execute permission.

curl -o runly -L https://repo.runly.io/exe/runly-0.4.49-linux-x64
chmod +x runly

Running the Node

A cluster API key will need to be set in order to be able to connect the node to your organization. The API key is stored in a settings.json file in the user profile of the account the runly-node service is going to run as. The set-apikey command should be run as the service account user.

Set the API Key:

runly set-apikey <api-key>

Enable and start the service:

sudo systemctl enable runly-node
sudo systemctl start runly-node