Configuration

Set application environment variables before starting the process. They are read when conda-presto imports its configuration. Conda settings come from the active conda context. CLI flags override only the corresponding options.

Integer settings use decimal strings. Boolean settings accept 1, true, yes, 0, false or no, ignoring case. Empty values use defaults. Comma-separated settings trim whitespace and omit empty items. Invalid settings fail at startup.

Channels and platforms

HTTP requests use channels from the request, then the input file, then CONDA_PRESTO_CHANNELS. The CLI also considers conda’s effective channels. The server checks channels against CONDA_PRESTO_ALLOWED_CHANNELS using resolved URLs.

Request platforms are explicit, or default to the native platform. CONDA_PRESTO_PLATFORMS only selects startup warmup targets. Target virtual-package overrides and other effective conda virtual records participate in result-cache identity.

Execution and storage

CONDA_PRESTO_CONCURRENCY limits simultaneous foreground requests. CONDA_PRESTO_WORKERS controls processes within a multiplatform solve. Persistent mode reuses one worker and its indexes. The server image enables that mode with one foreground slot.

When no backend is explicit, a Redis URL selects Redis, otherwise a configured directory selects file storage, otherwise memory is used. See Cache reference for limits and freshness.

Optional providers

Install conda-presto[sbom] or conda-presto[sigstore] into the service environment. The locked Pixi artifacts environment includes both and can be selected in the canonical image build. Provider availability and signing configuration are reported through /capabilities.

Signing requires explicit enablement and a configured trust choice. A trust-file path alone does not enable signing. Verification receives the recipient’s expected identity and issuer with the request. See Environment variable reference for exact settings and HTTP API for fields.

Source workspace

prod runs the base service, artifacts adds optional providers, cli runs one-shot commands, test includes provider checks, dev provides lint and server tools, and docs builds Sphinx. Changing Pixi metadata requires regenerating pixi.lock.