bino setup
bino relies on Chrome headless shell and a template engine to render PDFs, and on DuckDB extensions
to read your data. Use bino setup to download and configure these dependencies.
bino setup [flags]Template engine flags
Section titled “Template engine flags”--template-engine– download or update the bn-template-engine.--engine-version– specific template engine version to download (default: latest). For examplev0.37.0.
DuckDB extension flags
Section titled “DuckDB extension flags”--duckdb-extensions– download every DuckDB extension the CLI can use into the local cache.
General flags
Section titled “General flags”--dry-run– show what would be installed without actually downloading.--quiet– suppress verbose installer output.
Examples
Section titled “Examples”Install Chrome headless shell and template engine:
bino setupInstall the template engine only (latest version):
bino setup --template-engineInstall a specific template engine version:
bino setup --template-engine --engine-version v0.37.0Install the DuckDB extensions only:
bino setup --duckdb-extensionsPreview what would be installed without downloading:
bino setup --dry-runChrome headless shell
Section titled “Chrome headless shell”Chrome headless shell (chrome-headless-shell) is a lightweight Chrome binary purpose-built for headless rendering. It is downloaded from Google's Chrome for Testing infrastructure and cached in ~/.bino/chrome-headless-shell/.
If you need to use a custom Chrome or Chromium installation, set the CHROME_PATH environment variable to point to the binary. This takes priority over the cached version.
Template engine
Section titled “Template engine”The template engine (bn-template-engine) is a JavaScript runtime used to render HTML templates. It is downloaded separately from Chrome headless shell and cached in ~/.bino/cdn/bn-template-engine/.
Multiple versions can be installed side by side. By default, bino uses the latest locally installed version unless a specific version is pinned in bino.toml via the engine-version field. See Project configuration for more details.
DuckDB extensions
Section titled “DuckDB extensions”bino queries data through DuckDB, which loads extensions on demand — excel and httpfs for file and URL sources, postgres and mysql for databases, prql for PRQL datasets, and webdavfs for WebDAV secrets. They are normally downloaded the first time they are needed and cached in ~/.bino/cache/duckdb/extensions/.
bino setup --duckdb-extensions downloads all of them up front. Use it to prepare an air-gapped machine, or to warm a CI cache so builds never block on an extension download:
bino setup --duckdb-extensionsExtensions are version- and platform-specific, so the cache from one machine only transfers to another with the same OS, architecture, and bino release.
Troubleshooting
Section titled “Troubleshooting”If builds fail with rendering or browser errors, rerun this command and verify that your environment has network and disk access.