Environment variable reference#
conda-presto reads these settings when its configuration module is imported. The scope column distinguishes direct solves, public HTTP servers, and the broker-only solver service.
Direct solve settings#
These settings affect conda presto and public HTTP resolve operations. The
internal conda --solver=presto path captures effective state from the calling
conda process instead.
Variable |
Default |
Scope |
Purpose |
|---|---|---|---|
|
|
Direct CLI and HTTP |
HTTP fallback when no request or input file supplies channels. CLI fallback when conda’s effective channels are empty or only |
|
|
Direct multi-platform solves |
Process-pool size for platforms within one request. |
|
|
Direct solve processes |
Maximum retained rattler indexes. Set to |
|
|
Direct Linux solves |
Injected virtual |
|
|
Direct Linux solves |
Injected virtual |
|
|
Direct macOS solves |
Injected virtual |
|
|
Direct Windows solves |
Injected virtual |
Direct CLI and public HTTP solves apply these target-model overrides for each requested Linux, macOS, or Windows target, including the host’s native subdir. The resulting effective records can also include other virtual-package plugin detections or overrides, such as CUDA or architecture records. The public result-cache identity captures those effective records per requested platform. The internal Presto solver does not use these four defaults. It serializes and restores the calling conda process’s effective virtual-package records. Those records also participate in private solver cache identity.
HTTP server settings#
Variable |
Default |
Purpose |
|---|---|---|
|
|
Platforms whose configured channels are warmed before readiness. This is not the default platform list for a request. |
|
value of |
Accepted HTTP request channels after exact resolved-URL comparison. |
|
|
Maximum simultaneous foreground solve requests. Docker and the broker provider set |
|
|
Maximum HTTP request body. Excess returns HTTP 413. |
|
|
Maximum specs in one request. |
|
|
Maximum channels in one request. |
|
|
Maximum platforms in one request. |
|
|
Maximum channels in the private broker solver protocol. |
|
|
Maximum combined items across requested additions, removals, installed records, history, pins, virtual packages, aggressive updates, and always-update entries in the private broker solver protocol. |
|
|
Server ceiling for returned repair suggestions. |
|
|
Server ceiling for evaluated repair candidates. |
|
|
Server ceiling for repair wall time in milliseconds. |
|
|
Solver deadline used by HTTP requests, the internal solver client, and scheduled refresh where lower than fixed limits. Non-abandoned cache-state inspection can extend observed request duration. |
|
|
HTTP file-parse timeout. |
|
|
Default for the |
|
|
Default for the |
|
|
Route HTTP solves through one worker that retains loaded repodata and indexes. Set by Docker and the broker provider. |
|
|
Requests per minute per client IP. Set to |
|
unset |
Comma-separated browser origins. CORS middleware is absent when unset. |
|
|
Application logger level: |
Request-cap violations return HTTP 400 unless the body limit applies. Repair query values below the configured ceilings narrow one request. Values above the ceilings are clamped.
Result cache settings#
These settings apply to any HTTP application process, including Docker and the broker service. One-shot CLI output does not use the HTTP result cache.
Variable |
Default |
Purpose |
|---|---|---|
|
|
Combined in-process entry limit for public resolve responses and private solver final states. |
|
|
Combined encoded payload limit in MiB. Set to |
|
automatic |
|
|
unset |
Directory required by the file backend. Selecting no backend but setting this value selects file storage. |
|
unset |
Redis URL. Selecting Redis without a URL uses |
|
|
Redis key namespace. |
Negative entry or memory limits are rejected. File storage without a directory and unknown backend names are also rejected. See Cache reference for key and retention behavior.
Broker-only refresh settings#
These settings are loaded by every server process, but scheduled refresh is
enabled only for the persistent conda-presto.server broker child.
Variable |
Default |
Purpose |
|---|---|---|
|
|
Maximum recorded requests in the candidate catalog, plus the same observation capacity. Set to |
|
|
Best-effort checkpointing of requests without detected credentials. Requires file or Redis storage. |
|
|
Seconds between scheduled cycles. Set to |
|
|
Maximum eligible requests considered per cycle. Must be positive. |
The first cycle has a fixed 30-second delay. Fixed per-operation and cycle budgets are documented in Cache reference.
Broker-injected variables#
conda-broker supplies these values to the service child. They are integration state, not normal user configuration.
Variable |
Value |
Consumer |
|---|---|---|
|
|
Enables the guarded private solver route and scheduled refresh. |
|
Allocated loopback endpoint |
Broker health-check command and service consumers. |
|
Allocated port |
Uvicorn bind configuration. |
The provider also overrides host, concurrency, rate limiting, persistent-worker mode, and conda file locking. See Broker service reference.
Pixi activation settings#
The repository’s Pixi environments set these conda variables for solve-only workloads:
Variable |
Value |
Effect |
|---|---|---|
|
|
Select rattler in conda context before conda-presto applies its direct-engine requirement. |
|
|
Prefer higher-priority channels. |
|
|
Disable conda filesystem locking in the shared Pixi activation. The Docker server and broker child override this to |
|
|
Disable conda’s additional unsatisfiable hint generation. |
|
|
Suppress channel notices. |
|
empty |
Disable forced aggressive updates. |
|
|
Reuse local repodata under conda’s effective cache policy. |
|
|
Suppress progress-oriented conda output. |
The Docker server applies CONDA_NO_LOCK=false after its Pixi shell hook, and
the broker child injects the same value. Their persistent worker processes
share conda’s package cache. The one-shot CLI image keeps the Pixi activation
default.