Install on an offline machine

A verification needs no network. Installing the verifier does, once: to fetch its dependencies and, for the Python package, the build backend. This guide does that part on a connected machine and carries the result to the offline one.

Run the connected steps on a machine with the same operating system, processor architecture and Python minor version as the offline machine. cryptography ships compiled wheels, so a wheel fetched for another platform does not install.

Python: on the connected machine

Clone the verifier at the release tag and fetch every file its installation needs into a wheelhouse directory: its dependencies, and the build backend, the exact setuptools version its pyproject.toml requires, which pip needs to build the package from its checkout.

git clone --branch v0.1.0 https://github.com/loquitur-dev/loquitur-verify-py.git
python -m pip download --dest wheelhouse ./loquitur-verify-py "setuptools==84.0.0"

Copy the loquitur-verify-py directory and the wheelhouse directory to the offline machine.

Python: on the offline machine

From the directory that holds both copies, install from the local files only:

python -m pip install --no-index --find-links wheelhouse ./loquitur-verify-py
loquitur-verify --version

--no-index stops pip from looking for anything on a package index, so a missing file is an error rather than a download.

python -m pip install --no-index --find-links wheelhouse .\loquitur-verify-py
loquitur-verify --version

TypeScript: on the connected machine

Build the package tarball, then install it into the project that will use it. The runtime dependencies of @loquitur/verify are JavaScript only, so the packages npm installs in the project work on any platform Node.js runs on.

git clone --branch v0.1.0 https://github.com/loquitur-dev/loquitur-verify-ts.git
cd loquitur-verify-ts
npm ci
npm pack
cd ../your-project
npm install ../loquitur-verify-ts/loquitur-verify-0.1.0.tgz

TypeScript: on the offline machine

Copy your-project, with the packages npm installed in it and its package-lock.json, to the offline machine. Nothing else is installed there.

Check the installation offline

Verify a bundle you carried over, as in the Python tutorial or the TypeScript tutorial. A run never contacts a network. A run that ends in HOST_FAILURE means the host failed an operation on your input; the outcome table says what that does and does not mean.