Install

Release builds need no Python and run on Linux with glibc 2.28 or newer: RHEL, Rocky and Alma Linux 8+, Debian 10+, Ubuntu 20.04+, on x86_64 (and aarch64 where published).

Download	Use it when
pageclerk-VERSION-linux-x86_64.tar.gz	You want the fastest start (about 0.3 s). Unpack anywhere.
pageclerk-VERSION-linux-x86_64-onefile	You want one file to copy around (about 0.6 s per start).
pageclerk_VERSION_amd64.deb / pageclerk-VERSION-1.x86_64.rpm	You manage servers with packages.
Container image	You run tools in containers.

# Standalone folder
tar -xzf pageclerk-VERSION-linux-x86_64.tar.gz
sudo ln -s "$PWD/pageclerk-VERSION-linux-x86_64/pageclerk" /usr/local/bin/pageclerk

# Single file
sudo install -m 755 pageclerk-VERSION-linux-x86_64-onefile /usr/local/bin/pageclerk

# Packages (install to /opt/pageclerk, command /usr/bin/pageclerk)
sudo apt install ./pageclerk_VERSION_amd64.deb
sudo dnf install ./pageclerk-VERSION-1.x86_64.rpm

# Container
docker run --rm -v "$PWD":/work pageclerk:VERSION build -c job.yaml

Check the download against SHA256SUMS:

sha256sum -c SHA256SUMS --ignore-missing

The single-file build unpacks itself once into ~/.cache/pageclerk/VERSION (not /tmp, which is often noexec on servers). Scripts that call PageClerk many times in a loop start faster with the standalone folder or a package.

Then install your license key; PageClerk needs one to produce PDFs.