Release binary
Each release on GitHub has a tarball per platform and a SHA-256 checksum next to it.
| Target | Platform | File |
|---|---|---|
x86_64-unknown-linux-gnu | Linux x86_64 | virling-v0.1.0-x86_64-unknown-linux-gnu.tar.gz |
aarch64-unknown-linux-gnu | Linux arm64 | virling-v0.1.0-aarch64-unknown-linux-gnu.tar.gz |
aarch64-apple-darwin | macOS on Apple silicon | virling-v0.1.0-aarch64-apple-darwin.tar.gz |
The name is always virling-vX.Y.Z-<target>.tar.gz, with the checksum at the same name plus .sha256. Each tarball holds one folder with the virling binary and the LICENSE file.
Builds for Intel macOS and Windows are Not available yet. Use Docker or build from source.
Download and verify
V=0.1.0
T=x86_64-unknown-linux-gnu
curl -LO https://github.com/virling/virling/releases/download/v$V/virling-v$V-$T.tar.gz
curl -LO https://github.com/virling/virling/releases/download/v$V/virling-v$V-$T.tar.gz.sha256
shasum -a 256 -c virling-v$V-$T.tar.gz.sha256
tar xzf virling-v$V-$T.tar.gz
sudo install virling-v$V-$T/virling /usr/local/bin/virling
shasum -a 256 -c prints OK when the file matches. On Linux without shasum, use sha256sum -c.
The Linux builds link against glibc and are built on Ubuntu runners. They run on current Debian, Ubuntu, Fedora and similar distributions.
Check it runs
$ virling --version
virling 0.1.0
Next: run the binary in production, optionally as a systemd service.