docs/reference/cli/pixi/upload/index.md
Upload conda packages to various channels
--8<-- "docs/reference/cli/pixi/upload_extender:description"
pixi upload [OPTIONS] [PACKAGE_FILES]... <COMMAND>
| Command | Description |
|---|---|
quetz | Upload to a Quetz server. Authentication is used from the keychain / auth-file |
artifactory | Options for uploading to an Artifactory channel |
prefix | Options for uploading to a prefix.dev server. Authentication is used from the keychain / auth-file |
anaconda | Options for uploading to a Anaconda.org server |
cloudsmith | Options for uploading to a Cloudsmith repository. Authentication is used from the keychain / auth-file |
s3 | Options for uploading to S3 |
<PACKAGE_FILES></a>
: The package file to uploadMay be provided more than once.
--offline=<OFFLINE></a>
: Run without network access. Uploading always requires the network, so this makes pixi upload fail fast instead of attempting to connect. Defined here rather than through the shared config flags because UploadOpts already owns --auth-fileenv: PIXI_OFFLINE
options: y, yes, t, true, on, 1, n, no, f, false, off, 0
--allow-insecure-host <ALLOW_INSECURE_HOST></a>
: List of hosts for which SSL certificate verification should be skippedMay be provided more than once.
--no-config</a>
: Don't read system or user-level configuration files. Project-local <project>/.pixi/config.toml is still loadedenv: PIXI_NO_CONFIG
default: false
--config-file <PATH></a>
: Load configuration from this file instead of searching system and user-level paths. Project-local <project>/.pixi/config.toml is still merged on topenv: PIXI_CONFIG_FILE
Upload conda packages to various channels
Supported server types: prefix, anaconda, quetz, artifactory, s3, conda-forge
Use pixi auth login to authenticate with the server.
--8<-- "docs/reference/cli/pixi/upload_extender:example"