Pixi

https://pixi.prefix.dev/latest/
Admin
Pixi is a fast, modern, and reproducible package management tool for developers that supports...
Tokens:152,473
Snippets:2,220
Trust Score:9.2
Update:2 months ago
Show doc for...
Tokens:
Raw
### pixi install examples

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/install

Common usage patterns for the install command, including path specification, frozen/locked modes, and environment selection.

```bash
pixi install  
pixi install --manifest-path ~/myworkspace/pixi.toml 
pixi install --frozen 
pixi install --locked 
pixi install --environment lint 
pixi install -e lint 
```

--------------------------------

### Successful project build

Source: https://pixi.prefix.dev/latest/tutorials/rust

Example output after successfully installing the required system dependencies.

```text
pixi run build
...
   Compiling git2 v0.18.3
   Compiling my_rust_project v0.1.0 (/my_rust_project)
    Finished dev [unoptimized + debuginfo] target(s) in 7.44s
     Running `target/debug/my_rust_project`
```

--------------------------------

### Install Global Packages

Source: https://pixi.prefix.dev/latest/concepts/package_specifications

Examples of installing packages globally with specific version and build constraints.

```bash
# Install a specific version
pixi global install python=3.11

# Install with version constraints
pixi global install "numpy>=1.21,<2.0"

# Install a specific build (e.g., CUDA-enabled package) using = syntax
pixi global install "pytorch=*=cuda*"

# Alternative bracket syntax for build specification
pixi global install "pytorch [build='cuda*']"

# Specify both version and build using bracket syntax
pixi global install "pytorch [version='2.9.*', build='cuda*']"
```

--------------------------------

### Advanced Global Installation Options

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/install

Examples demonstrating channel selection, matchspec usage, platform targeting, and environment management.

```bash
pixi global install jupyter --with polars
```

```bash
pixi global install --expose python3.8=python python=3.8
```

```bash
pixi global install --environment science --expose jupyter --expose ipython jupyter ipython polars
```

```bash
pixi global install --channel conda-forge --channel bioconda trackplot
```

```bash
pixi global install python=3.9.*
pixi global install "python [version='3.11.0', build_number=1]"
pixi global install "python [version='3.11.0', build=he550d4f_1_cpython]"
pixi global install python=3.11.0=h10a6764_1_cpython
```

```bash
pixi global install --platform osx-64 ruff
```

```bash
pixi global install ipython --with numpy --with scipy
```

```bash
pixi global install --environment data-science ipython jupyterlab numpy matplotlib
```

```bash
pixi global install --expose "py39=python3.9" "python=3.9.*"
```

--------------------------------

### Environment package list

Source: https://pixi.prefix.dev/latest/python/tutorial

Example output showing installed packages in an environment.

```text
package          version       build               size       kind   source
...
pytest           8.1.1                             1.1 mib    pypi   pytest-8.1.1-py3-none-any.whl
...
```

--------------------------------

### Example Manifest with Shortcuts

Source: https://pixi.prefix.dev/latest/global_tools/manifest

A sample manifest configuration showing the shortcuts entry used by pixi to register applications in the start menu.

```toml
[envs.mss]
channels = ["https://prefix.dev/conda-forge"]
dependencies = { mss = "*" }
exposed = { ... }
shortcuts = ["mss"]
```

--------------------------------

### Install and run Pixi extensions

Source: https://pixi.prefix.dev/latest/CHANGELOG

Demonstrates how to install a global Pixi extension and execute it.

```bash
pixi global install pixi-pack
pixi pack
```

--------------------------------

### Deploy with Docker

Source: https://pixi.prefix.dev/latest/workspace/multi_environment

Example Dockerfile using Pixi to install production dependencies and serve the application.

```dockerfile
FROM ghcr.io/prefix-dev/pixi:latest # this doesn't exist yet
WORKDIR /app
COPY . .
RUN pixi run --environment prod postinstall
EXPOSE 8080
CMD ["/usr/local/bin/pixi", "run", "--environment", "prod", "serve"]
```

--------------------------------

### Install multiple packages from source

Source: https://pixi.prefix.dev/latest/global_tools/manifest

Install multiple packages from a local workspace path.

```bash
pixi global install --path ./workspace foo bar
```

--------------------------------

### Install Pixi on Windows

Source: https://pixi.prefix.dev/latest

Use PowerShell to download and execute the installation script.

```powershell
powershell -ExecutionPolicy ByPass -c "irm -useb https://pixi.sh/install.ps1 | iex"
```

--------------------------------

### Install local package files

Source: https://pixi.prefix.dev/latest/concepts/package_specifications

Install a pre-built package directly from a local filesystem path.

```bash
pixi add /path/to/package-1.0-hb0f4dca_0.conda
```

--------------------------------

### Basic Global Installation

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/install

Install one or more packages globally using default settings.

```bash
pixi global install starship nushell ripgrep bat
```

```bash
pixi global install ruff
# Multiple packages can be installed at once
pixi global install starship rattler-build
```

--------------------------------

### Examples of pixi init usage

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/init

Various command-line examples demonstrating how to initialize projects with different configurations, platforms, and import files.

```bash
pixi init myproject  
pixi init ~/myproject  
pixi init  
pixi init --channel conda-forge --channel bioconda myproject  
pixi init --platform osx-64 --platform linux-64 myproject  
pixi init --import environment.yml  
pixi init --format pyproject  
pixi init --format pixi --scm gitlab
```

--------------------------------

### Configuration examples for pixi

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/config/set

Various examples demonstrating how to set channels, mirrors, system flags, and environment paths.

```bash
pixi config set default-channels '["conda-forge", "bioconda"]'
pixi config set --global mirrors '{"https://conda.anaconda.org/conda-forge": ["https://prefix.dev/conda-forge"]}'
pixi config set repodata-config.disable-zstd true --system
pixi config set --global detached-environments "/opt/pixi/envs"
pixi config set detached-environments false
pixi config set s3-options.my-bucket '{"endpoint-url": "http://localhost:9000", "force-path-style": true, "region": "auto"}'
```

--------------------------------

### Install project dependencies

Source: https://pixi.prefix.dev/latest/python/tutorial

Manually trigger the installation of the environment based on the manifest.

```bash
pixi install
```

--------------------------------

### Token, Basic, and S3 Authentication Examples

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/auth/login

Examples for manual token, basic authentication, and S3 credential configuration.

```bash
pixi auth login repo.prefix.dev --token pfx_JQEV-m_2bdz-D8NSyRSaAndHANx0qHjq7f2iD
pixi auth login anaconda.org --conda-token ABCDEFGHIJKLMNOP
pixi auth login https://myquetz.server --username john --password xxxxxx
pixi auth login s3://my-bucket --s3-access-key-id $AWS_ACCESS_KEY_ID --s3-secret-access-key $AWS_SECRET_ACCESS_KEY
```

--------------------------------

### Docker Environment Setup

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/shell-hook

Example of using shell-hook to persist environment activation in a Docker container without the pixi executable.

```bash
pixi shell-hook --shell bash > /etc/profile.d/pixi.sh
rm ~/.pixi/bin/pixi # Now the environment will be activated without the need for the pixi executable.
```

--------------------------------

### OAuth Authentication Examples

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/auth/login

Examples for authenticating against prefix.dev, self-hosted OIDC providers, and headless environments.

```bash
pixi auth login prefix.dev
```

```bash
pixi auth login my.private.host \
    --oauth \
    --oauth-issuer-url https://idp.example.com \
    --oauth-client-id my-cli-client
```

```bash
pixi auth login prefix.dev --oauth-flow device-code
```

--------------------------------

### Install tools from source

Source: https://pixi.prefix.dev/latest/global_tools/manifest

Install a tool directly from a git repository or a local path.

```bash
pixi global install --git https://github.com/prefix-dev/rattler-build rattler-build
pixi global install --path ./my-tool
```

--------------------------------

### Install Pixi via Scoop

Source: https://pixi.prefix.dev/latest/installation

Use the Scoop command-line installer to install Pixi on Windows.

```bash
scoop install main/pixi
```

--------------------------------

### Select Build Installer

Source: https://pixi.prefix.dev/latest/build/backends/pixi-build-python

Choose the tool used to install the built wheel into the prefix.

```toml
[package.build.config]
installer = "pip"
```

--------------------------------

### Install a global tool

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Installs a package globally so it is available from any directory.

```bash
pixi global install rattler-build
```

--------------------------------

### Install a global tool

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Install a CLI tool globally using pixi.

```bash
pixi global install git
```

--------------------------------

### pixi install usage

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/install

Basic command structure for installing a pixi environment.

```bash
pixi install [OPTIONS]
```

--------------------------------

### Install pixi-browse globally

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_browse

Use the pixi global install command to add the tool to your environment.

```bash
pixi global install pixi-browse
```

--------------------------------

### Execute start task

Source: https://pixi.prefix.dev/latest/tutorials/rust

Runs the project using the newly created start task.

```bash
pixi run start
Hello, world!
```

--------------------------------

### Install pixi-pack and pixi-unpack

Source: https://pixi.prefix.dev/latest/deployment/pixi_pack

Install the necessary tools globally using the pixi package manager.

```bash
pixi global install pixi-pack pixi-unpack
```

--------------------------------

### Set workspace description example

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/workspace/description/set

Example command to set the workspace description to a specific string.

```bash
pixi workspace description set "My awesome workspace"
```

--------------------------------

### Install Pixi extensions using global

Source: https://pixi.prefix.dev/latest/integration/extensions/introduction

Use the global install command to manage extensions in isolated environments.

```bash
# Install a single extension
pixi global install pixi-pack

# Install multiple extensions at once
pixi global install pixi-pack pixi-diff
```

--------------------------------

### Install and expose tool with custom name

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Installs a package and maps its executable to a specific name on the system PATH.

```bash
pixi global install --expose py3=python "python=3.12"
```

--------------------------------

### Pixi pyproject.toml Configuration Example

Source: https://pixi.prefix.dev/latest/python/pyproject_toml

A comprehensive example showing project metadata, workspace channels, platforms, dependencies, tasks, and environment definitions.

```toml
[project]
name = "my_project"
requires-python = ">=3.9"
dependencies = [
    "numpy",
    "pandas",
    "matplotlib",
    "ruff",
]

[tool.pixi.workspace]
channels = ["conda-forge"]
platforms = [
    "osx-arm64",
    "osx-64",
    { platform = "linux-64", cuda = "11.0" },
    { platform = "win-64", cuda = "11.0" },
]

[tool.pixi.dependencies]
compilers = "*"
cmake = "*"

[tool.pixi.tasks]
start = "python my_project/main.py"
lint = "ruff lint"

[tool.pixi.feature.test.dependencies]
pytest = "*"

[tool.pixi.feature.test.tasks]
test = "pytest"

[tool.pixi.environments]
test = ["test"]
```

--------------------------------

### Install keyring with providers

Source: https://pixi.prefix.dev/latest/deployment/authentication

Install the keyring package and optional backend plugins for specific artifact registries.

```bash
pixi global install keyring
```

```bash
pixi global install keyring --with keyrings.google-artifactregistry-auth
```

```bash
pixi global install keyring --with keyrings.artifacts
```

```bash
pixi global install keyring --with keyrings.codeartifact
```

--------------------------------

### Example of removing packages

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/remove

A practical example showing how to remove multiple packages from a specific environment.

```bash
pixi global remove -e my-env package1 package2
```

--------------------------------

### pixi task add examples

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/task/add

Various examples of adding tasks with different options such as working directories, dependencies, platforms, and environment variables.

```bash
pixi task add cow cowpy "Hello User"
pixi task add tls ls --cwd tests
pixi task add test cargo t --depends-on build
pixi task add build-osx "METAL=1 cargo build" --platform osx-64
pixi task add train python train.py --feature cuda
pixi task add serve "python serve.py" --environment dev
pixi task add publish-pypi "hatch publish --yes --repo main" --feature build --env HATCH_CONFIG=config/hatch.toml --description "Publish the package to pypi"
```

--------------------------------

### Pixi list output example

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/list

Example output of the pixi list command showing package details like version, build, size, and source.

```text
➜ pixi list
 Package           Version     Build               Size       Kind   Source
 _libgcc_mutex     0.1         conda_forge         2.5 KiB    conda  _libgcc_mutex-0.1-conda_forge.tar.bz2
 _openmp_mutex     4.5         2_gnu               23.1 KiB   conda  _openmp_mutex-4.5-2_gnu.tar.bz2
 bzip2             1.0.8       hd590300_5          248.3 KiB  conda  bzip2-1.0.8-hd590300_5.conda
 ca-certificates   2023.11.17  hbcca054_0          150.5 KiB  conda  ca-certificates-2023.11.17-hbcca054_0.conda
 ld_impl_linux-64  2.40        h41732ed_0          688.2 KiB  conda  ld_impl_linux-64-2.40-h41732ed_0.conda
 libexpat          2.5.0       hcb278e6_1          76.2 KiB   conda  libexpat-2.5.0-hcb278e6_1.conda
 libffi            3.4.2       h7f98852_5          56.9 KiB   conda  libffi-3.4.2-h7f98852_5.tar.bz2
 libgcc-ng         13.2.0      h807b86a_4          755.7 KiB  conda  libgcc-ng-13.2.0-h807b86a_4.conda
 libgomp           13.2.0      h807b86a_4          412.2 KiB  conda  libgomp-13.2.0-h807b86a_4.conda
 libnsl            2.0.1       hd590300_0          32.6 KiB   conda  libnsl-2.0.1-hd590300_0.conda
 libsqlite         3.44.2      h2797004_0          826 KiB    conda  libsqlite-3.44.2-h2797004_0.conda
 libuuid           2.38.1      h0b41bf4_0          32.8 KiB   conda  libuuid-2.38.1-h0b41bf4_0.conda
 libxcrypt         4.4.36      hd590300_1          98 KiB     conda  libxcrypt-4.4.36-hd590300_1.conda
 libzlib           1.2.13      hd590300_5          60.1 KiB   conda  libzlib-1.2.13-hd590300_5.conda
 ncurses           6.4         h59595ed_2          863.7 KiB  conda  ncurses-6.4-h59595ed_2.conda
 openssl           3.2.0       hd590300_1          2.7 MiB    conda  openssl-3.2.0-hd590300_1.conda
 python            3.12.1      hab00c5b_1_cpython  30.8 MiB   conda  python-3.12.1-hab00c5b_1_cpython.conda
 readline          8.2         h8228510_1          274.9 KiB  conda  readline-8.2-h8228510_1.conda
 tk                8.6.13      noxft_h4845f30_101  3.2 MiB    conda  tk-8.6.13-noxft_h4845f30_101.conda
 tzdata            2023d       h0c530f3_0          116.8 KiB  conda  tzdata-2023d-h0c530f3_0.conda
 xz                5.2.6       h166bdaf_0          408.6 KiB  conda  xz-5.2.6-h166bdaf_0.tar.bz2
```

--------------------------------

### Install multiple tools

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Install multiple tools simultaneously without specifying an environment.

```bash
pixi global install pixi-pack rattler-build
```

--------------------------------

### Tree Output Example

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/tree

Example output showing the dependency structure of a workspace.

```text
➜ pixi tree
├── pre-commit v3.3.3
│   ├── cfgv v3.3.1
│   │   └── python v3.12.2
│   │       ├── bzip2 v1.0.8
│   │       ├── libexpat v2.6.2
│   │       ├── libffi v3.4.2
│   │       ├── libsqlite v3.45.2
│   │       │   └── libzlib v1.2.13
│   │       ├── libzlib v1.2.13 (*)
│   │       ├── ncurses v6.4.20240210
│   │       ├── openssl v3.2.1
│   │       ├── readline v8.2
│   │       │   └── ncurses v6.4.20240210 (*)
│   │       ├── tk v8.6.13
│   │       │   └── libzlib v1.2.13 (*)
│   │       └── xz v5.2.6
│   ├── identify v2.5.35
│   │   └── python v3.12.2 (*)
...
└── tbump v6.9.0
...
    └── tomlkit v0.12.4
        └── python v3.12.2 (*)
```

--------------------------------

### Install pixi-skills

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_skills

Install the pixi-skills tool globally using the pixi package manager.

```bash
pixi global install pixi-skills
```

--------------------------------

### Command usage syntax

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/install

General usage pattern for the global install command.

```bash
pixi global install [OPTIONS] [PACKAGE]...
```

--------------------------------

### Examples of uninstalling global environments

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/uninstall

Common usage examples for removing one or multiple environments.

```bash
pixi global uninstall my-env
pixi global uninstall pixi-pack rattler-build
```

--------------------------------

### Install Pixi Diff Tools

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_diff

Install the required tools globally using pixi.

```bash
pixi global install pixi-diff pixi-diff-to-markdown glow-md
```

--------------------------------

### Pass Extra Arguments to Installer

Source: https://pixi.prefix.dev/latest/build/backends/pixi-build-python

Provide additional arguments to the selected installer, such as configuration settings.

```toml
[package.build.config]
extra-args = ["-Cbuilddir=mybuilddir"]
```

```toml
[package.build.config]
extra-args = ["-Cbuilddir=mybuilddir"]

[package.build.target.win-64.config]
extra-args = ["-Cbuilddir=foo"]
# Result for win-64: ["-Cbuilddir=foo"]
```

--------------------------------

### Examples of removing exposed binaries

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/expose/remove

Examples showing how to remove one or multiple exposed binaries.

```bash
pixi global expose remove python
pixi global expose remove py310 python3
```

--------------------------------

### Install Pixi on Linux and macOS

Source: https://pixi.prefix.dev/latest

Use the curl command to download and execute the installation script.

```bash
curl -fsSL https://pixi.sh/install.sh | sh
```

--------------------------------

### Pixi install warning output

Source: https://pixi.prefix.dev/latest/workspace/multi_platform_configuration

Example of the warning message displayed when running pixi install on an unsupported platform.

```text
❯ pixi install
 WARN Not installing dependency for (default) on current platform: (osx-arm64) as it is not part of this project's supported platforms.
```

--------------------------------

### Example usage of pixi config append

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/config/append

Examples showing how to append channels to the default-channels configuration locally and globally.

```bash
pixi config append default-channels robostack
pixi config append default-channels bioconda --global
```

--------------------------------

### Install specific output from a multi-output package

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Command to target a specific package output when installing from a path.

```bash
pixi global install --path /path/to/package foobar
```

--------------------------------

### Examples of pixi config list

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/config/list

Common usage examples for listing configuration values, including filtering by key, JSON output, and scope selection.

```bash
pixi config list default-channels
pixi config list --json
pixi config list --system
pixi config list -g
```

--------------------------------

### Install pixi-install-to-prefix globally

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_install_to_prefix

Use this command to install the tool globally via the Pixi package manager.

```bash
pixi global install pixi-install-to-prefix
```

--------------------------------

### Manifest Entry for Platform-Specific Package

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Example of the manifest configuration generated when installing for a specific platform.

```toml
[envs.python]
channels = ["conda-forge"]
platforms = ["osx-64"]
dependencies = { python = "*" }
# ...
```

--------------------------------

### Install from source without a manifest

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Command to install a repository by explicitly specifying the build backend when no manifest exists.

```bash
pixi global install --git https://github.com/BurntSushi/xsv.git --build-backend pixi-build-rust
```

--------------------------------

### pixi auth logout examples

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/auth/logout

Examples showing how to remove authentication for specific hosts or storage locations.

```bash
pixi auth logout <HOST>
pixi auth logout repo.prefix.dev
pixi auth logout anaconda.org
pixi auth logout s3://my-bucket
```

--------------------------------

### Install Pixi via Winget

Source: https://pixi.prefix.dev/latest/installation

Use the Windows Package Manager to install Pixi on Windows systems.

```bash
winget install prefix-dev.pixi
```

--------------------------------

### Project Configuration Examples

Source: https://pixi.prefix.dev/latest/switching_from/uv

Comparison of project configuration formats for uv and Pixi.

```toml
[project]
name = "myproject"
version = "0.1.0"
requires-python = ">=3.12"
dependencies = [
    "numpy>=1.26",
    "pandas>=2.0",
]

[dependency-groups]
dev = ["pytest>=8.0"]
```

```toml
[workspace]
name = "myproject"
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64", "win-64"]

[dependencies]
python = ">=3.12"
numpy = ">=1.26"
pandas = ">=2.0"

[environments.test.dependencies]
pytest = ">=8.0"
```

```toml
[project]
name = "myproject"
version = "0.1.0"
requires-python = ">=3.12"
dependencies = [
    "numpy>=1.26",
    "pandas>=2.0",
]

[dependency-groups]
test = ["pytest>=8.0"]

[tool.pixi.workspace]
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64", "win-64"]

[tool.pixi.environments]
test = { features = ["test"], solve-group = "default" }
```

--------------------------------

### Manifest entry for multiple tools

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Example of the generated manifest structure when installing multiple tools at once.

```toml
[envs.pixi-pack]
channels = ["conda-forge"]
dependencies= { pixi-pack = "*" }
exposed = { pixi-pack = "pixi-pack" }

[envs.rattler-build]
channels = ["conda-forge"]
dependencies = { rattler-build = "*" }
exposed = { rattler-build = "rattler-build" }
```

--------------------------------

### Drop-in Installation (Linux/macOS)

Source: https://pixi.prefix.dev/latest/installation

Installs the Pixi binary directly into a specific directory without updating the system PATH.

```bash
curl -fsSL https://pixi.sh/install.sh | PIXI_BIN_DIR=/usr/local/bin PIXI_NO_PATH_UPDATE=1 bash
```

--------------------------------

### Install with Custom Channels

Source: https://pixi.prefix.dev/latest/global_tools/manifest

Specifies channel priority for package installation using the --channel flag.

```bash
pixi global install --channel conda-forge --channel bioconda snakemake
```

```toml
[envs.snakemake]
channels = ["conda-forge", "bioconda"]
dependencies = { snakemake = "*" }
exposed = { snakemake = "snakemake" }
```

--------------------------------

### Command Examples

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/add

Common usage patterns for adding packages and exposing executables within a specified environment.

```bash
pixi global add python=3.9.* --environment my-env
pixi global add python=3.9.* --expose py39=python3.9 --environment my-env
pixi global add numpy matplotlib --environment my-env
pixi global add numpy matplotlib --expose np=python3.9 --environment my-env
```

--------------------------------

### Configure Devcontainer Dockerfile

Source: https://pixi.prefix.dev/latest/integration/editor/vscode

Dockerfile setup for a Pixi-enabled devcontainer, including installation and shell completion.

```dockerfile
FROM mcr.microsoft.com/devcontainers/base:jammy

ARG PIXI_VERSION=v0.76.2

RUN curl -L -o /usr/local/bin/pixi -fsSL --compressed "https://github.com/prefix-dev/pixi/releases/download/${PIXI_VERSION}/pixi-$(uname -m)-unknown-linux-musl" \
    && chmod +x /usr/local/bin/pixi \
    && pixi info

# set some user and workdir settings to work nicely with vscode
USER vscode
WORKDIR /home/vscode

RUN echo 'eval "$(pixi completion -s bash)"' >> /home/vscode/.bashrc
```

--------------------------------

### pixi exec

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/exec

Run a command and install it in a temporary environment.

```APIDOC
## pixi exec

### Description
Run a command and install it in a temporary environment. The temporary environments can be removed with `pixi clean cache --exec`.

### Usage
`pixi exec [OPTIONS] [COMMAND]...`

### Arguments
- **COMMAND** - The executable to run, followed by any arguments. May be provided more than once.

### Options
- **--spec (-s)** (string) - Matchspecs of package to install. If not provided, the package is guessed from the command. May be provided more than once.
- **--with (-w)** (string) - Matchspecs of package to install, while also guessing a package from the command. May be provided more than once.
- **--channel (-c)** (string) - The channels to consider as a name or a url. May be provided more than once.
- **--platform (-p)** (string) - The platform to create the environment for. Defaults to the current machine's subdir.
- **--force-reinstall** (boolean) - If specified, a new environment is always created even if one already exists.
- **--list** (string) - Before executing the command, list packages in the environment. Specify `--list=some_regex` to filter.
- **--no-modify-ps1** (boolean) - Disable modification of the PS1 prompt to indicate the temporary environment.

### Examples
```
pixi exec python
pixi exec --with py-rattler --with numpy ipython
pixi exec --spec python=3.9 --spec numpy python
```
```

--------------------------------

### Add PyPI dependencies

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/add

Examples for adding Python packages from PyPI, including editable installs and git sources.

```bash
pixi add --pypi requests[security] 
pixi add --pypi Django==5.1rc1 
pixi add --pypi "boltons>=24.0.0" --feature lint 
pixi add --pypi "boltons @ https://files.pythonhosted.org/packages/46/35/e50d4a115f93e2a3fbf52438435bb2efcf14c11d4fcd6bdcd77a6fc399c9/boltons-24.0.0-py3-none-any.whl" 
pixi add --pypi "exchangelib @ git+https://github.com/ecederstrand/exchangelib" 
pixi add --pypi "project @ file:///absolute/path/to/project" 
pixi add --pypi "project@file:///absolute/path/to/project" --editable 
pixi add --git https://github.com/mahmoud/boltons.git boltons --pypi 
pixi add --git https://github.com/mahmoud/boltons.git boltons --branch main --pypi 
pixi add --git https://github.com/mahmoud/boltons.git boltons --rev e50d4a1 --pypi 
pixi add --git https://github.com/mahmoud/boltons.git boltons --tag v0.1.0 --pypi 
pixi add --git https://github.com/mahmoud/boltons.git boltons --tag v0.1.0 --pypi --subdirectory boltons
```

--------------------------------

### Install packages with different syntaxes

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/install

Demonstrates both equals and bracket syntax for specifying packages with build strings.

```bash
# Equals syntax (compact)
pixi global install "pytorch=*=*cuda*" --channel pytorch
pixi global install "jax=*=*cuda*"

# Bracket syntax (explicit)
pixi global install "pytorch [build='*cuda*']" --channel pytorch
pixi global install "jax [build='*cuda*']"
```

--------------------------------

### Manually install a Pixi extension

Source: https://pixi.prefix.dev/latest/integration/extensions/introduction

Install an extension by placing an executable file into a directory included in your system PATH.

```bash
# Download or build the extension
curl -L https://github.com/user/pixi-myext/releases/download/v1.0.0/pixi-myext -o pixi-myext
chmod +x pixi-myext
mv pixi-myext ~/.local/bin/
```

--------------------------------

### Complete Workspace Configuration

Source: https://pixi.prefix.dev/latest/deployment/artifactory

Example of a full workspace setup using Artifactory for internal packages and conda-forge as a fallback.

```toml
[workspace]
name = "my-project"
channels = ["https://my-org.jfrog.io/artifactory/internal-packages", "conda-forge"]
platforms = ["linux-64", "osx-arm64", "win-64"]

[dependencies]
python = ">=3.11"
# This will come from your Artifactory channel if available there
my-internal-package = "*"
# These will come from conda-forge (due to channel priority)
numpy = ">=1.24"
pandas = ">=2.0"
```

--------------------------------

### Platform-specific target configurations

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Examples of configuring activation scripts, dependencies, build dependencies, and tasks for the win-64 and osx-64 platforms.

```toml
[target.win-64.activation]
scripts = ["setup.bat"]

[target.win-64.dependencies]
msmpi = "~=10.1.1"

[target.win-64.build-dependencies]
vs2022_win-64 = "19.36.32532"

[target.win-64.tasks]
tmp = "echo $TEMP"

[target.osx-64.dependencies]
clang = ">=16.0.6"
```

--------------------------------

### pixi-install-to-prefix CLI usage

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_install_to_prefix

Displays the available arguments and options for the command-line interface.

```text
Usage: pixi-install-to-prefix [OPTIONS] <PREFIX>

Arguments:
  <PREFIX>  The path to the prefix where you want to install the environment

Options:
  -l, --lockfile <LOCKFILE>        The path to the pixi lock file [default: pixi.lock]
  -e, --environment <ENVIRONMENT>  The name of the pixi environment to install [default: default]
  -p, --platform <PLATFORM>        The platform you want to install for [default: <your-system-platform>]
  -c, --config <CONFIG>            The path to the pixi config file. By default, no config file is used
  -s, --shell <SHELL>              The shell(s) to generate activation scripts for. Default: see README
      --no-activation-scripts      Disable the generation of activation scripts
  -v, --verbose...                 Increase logging verbosity
  -q, --quiet...                   Decrease logging verbosity
  -h, --help                       Print help
```

--------------------------------

### Configure Malformed Wheel Installation

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Global or feature-specific setting to allow installation of wheels with non-standard filenames.

```toml
# Allow installing malformed wheels
skip-wheel-filename-check = true 
```

```toml
[feature.special.pypi-options]
# Only for this feature's environment
skip-wheel-filename-check = true
```

--------------------------------

### Skip workspace installation

Source: https://pixi.prefix.dev/latest/integration/ci/github_actions

Use the run-install option to install only the pixi binary without installing the current workspace.

```yaml
- uses: prefix-dev/setup-pixi@v0.10.0
  with:
    run-install: false
```

--------------------------------

### Execute tasks with pixi run

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/run

Examples demonstrating basic task execution, environment flags, and argument passing.

```bash
pixi run python
pixi run cowpy "Hey pixi user"
pixi run --manifest-path ~/myworkspace/pixi.toml python
pixi run --frozen python
pixi run --locked python
# If you have specified a custom task in the pixi.toml you can run it with run as well
pixi run build
# Extra arguments will be passed to the tasks command.
pixi run task argument1 argument2
# Use `--` to pass extra arguments directly to the underlying command,
# even when the task defines typed `args`.
pixi run task typed-arg-value -- --extra-flag --other=value
# Skip dependencies of the task
pixi run --skip-deps task
# Run in dry-run mode to see the commands that would be run
pixi run --dry-run task

# If you have multiple environments you can select the right one with the --environment flag.
pixi run --environment cuda python

# THIS DOESN'T WORK ON WINDOWS
# If you want to run a command in a clean environment you can use the --clean-env flag.
# The PATH should only contain the pixi environment here.
pixi run --clean-env "echo \$PATH"

# By default, CLI commands are not processed by the template engine.
# Use --templated to enable template rendering for ad-hoc commands.
pixi run --templated echo '{{ pixi.platform }}'
```

--------------------------------

### Install local .conda package globally

Source: https://pixi.prefix.dev/latest/CHANGELOG

Install a specific .conda package file directly using the global install command.

```bash
pixi global install --path /path/to/package-name.conda
```

--------------------------------

### List installed package

Source: https://pixi.prefix.dev/latest/python/tutorial

Check the installation details of a specific package.

```bash
pixi list pygments
```

--------------------------------

### Example Usage

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/global/expose/add

Common patterns for exposing binaries, including mapping names and direct exposure.

```bash
pixi global expose add python --environment my-env
pixi global expose add py310=python3.10 --environment python
```

--------------------------------

### Initialize a Node.js Workspace

Source: https://pixi.prefix.dev/latest

Commands to set up a Node.js project using Pixi.

```bash
pixi init pixi-node
cd pixi-node
```

```bash
pixi add nodejs
```

```javascript
console.log("Hello Pixi fans!");
```

```bash
pixi task add start "node hello.js"
```

```bash
pixi run start
```

--------------------------------

### Initialize and Run a Pixi Project

Source: https://pixi.prefix.dev/latest

Create a new project, add Python, and execute a command within the managed environment.

```bash
pixi init hello-world
cd hello-world
pixi add python
pixi run python -c 'print("Hello World!")'
```

--------------------------------

### Install conda-deny

Source: https://pixi.prefix.dev/latest/integration/third_party/conda_deny

Install the tool globally using the pixi package manager.

```bash
pixi global install conda-deny
```

--------------------------------

### Configure Build Backend Settings

Source: https://pixi.prefix.dev/latest/CHANGELOG

Example configuration for build backend channels, keys, and variant flags.

```toml
channels = ["https://prefix.dev/conda-forge"]
config = { key = "value" } # Optional configuration, specific to the build backend
flags = [
  "cuda",
  "blas_openblas",
] # Optional variant flags recorded in the package metadata
```

--------------------------------

### Initialize a new workspace

Source: https://pixi.prefix.dev/latest/tutorials/multi_environment

Create and enter a new project directory to begin workspace configuration.

```bash
pixi init production_project
cd production_project
```

--------------------------------

### Configure cross-architecture platform support

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Examples for supporting both native and emulated architectures on macOS and Windows.

```toml
# Specific environment for all platforms
platforms = ["osx-64", "osx-arm64", "win-64", "win-arm64"]
# Environments that run on both Intel and ARM setups but using the emulators:
platforms = ["osx-64", "win-64"]
```

--------------------------------

### Define Workspace Configuration

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Basic workspace setup defining channels and supported platforms.

```toml
[workspace]
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64", "win-64"]

[dependencies]
```

--------------------------------

### Define URL-based dependencies

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Install wheels or source distributions directly from a specific URL.

```toml
pandas = {url = "https://files.pythonhosted.org/packages/3d/59/2afa81b9fb300c90531803c0fd43ff4548074fa3e8d0f747ef63b3b5e77a/pandas-2.2.1.tar.gz"}
```

--------------------------------

### Configure workspace channels

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Examples of defining package channels using standard names, absolute file paths, or remote URLs.

```toml
channels = ["conda-forge", "robostack", "bioconda", "nvidia", "pytorch"]
```

```toml
channels = ["conda-forge", "file:///home/user/staged-recipes/build_artifacts"]
```

```toml
channels = ["conda-forge", "https://repo.prefix.dev/channel-name"]
```

--------------------------------

### Define Dependency Version Specifications

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Examples of various VersionSpec formats for defining package requirements.

```toml
# Use this exact package version
package0 = "==1.2.3"
# Use 1.2.3 up to 1.3.0
package1 = "~=1.2.3"
# Use larger than 1.2 lower and equal to 1.4
package2 = ">1.2,<=1.4"
# Bigger or equal than 1.2.3 or lower not including 1.0.0
package3 = ">=1.2.3|<1.0.0"
```

--------------------------------

### Example mapping JSON file

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

A JSON file format for mapping conda package names to PyPI package names.

```json
{
  "jupyter-ros": "my-name-from-mapping",
  "airflow": ["airflow", "apache-airflow"],
  "boltons": "boltons-pypi",
  "not-on-pypi": null
}

```

--------------------------------

### Basic setup-pixi usage

Source: https://pixi.prefix.dev/latest/integration/ci/github_actions

Standard configuration for the setup-pixi action, including authentication and running tests.

```yaml
- uses: prefix-dev/setup-pixi@v0.10.0
  with:
    pixi-version: v0.76.2
    cache: true
    auth-host: prefix.dev
    auth-token: ${{ secrets.PREFIX_DEV_TOKEN }}
- run: pixi run test
```

--------------------------------

### Define Git-based dependencies

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Install packages directly from Git repositories with support for revisions, subdirectories, and LFS.

```toml
# Note don't forget the `ssh://` or `https://` prefix!
pytest = { git = "https://github.com/pytest-dev/pytest.git"}
httpx = { git = "https://github.com/encode/httpx.git", rev = "c7c13f18a5af4c64c649881b2fe8dbd72a519c32"}
py-rattler = { git = "ssh://git@github.com/conda/rattler.git", subdirectory = "py-rattler" }
my-model = { git = "https://github.com/example/my-model.git", lfs = true }
```

--------------------------------

### Show Installed Skills

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_skills

Display the status of installed skills across all or specific backends.

```bash
# Show installed skills across all backends
pixi skills status

# Show installed skills for a specific backend
pixi skills status --backend claude
```

--------------------------------

### Define PyPI dependencies with extras

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Use the extras field to specify optional dependencies to install alongside the package.

```toml
pandas = { version = ">=1.0.0", extras = ["dataframe", "sql"]}
pytest = { git = "URL", extras = ["dev"]}
black = { url = "URL", extras = ["cli"]}
minimal-project = { path = "./minimal-project", editable = true, extras = ["dev"]}
```

--------------------------------

### Define CUDA feature channels and platforms

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Example of specifying channels and platforms within a feature definition.

```toml
[feature.cuda]
channels = ["nvidia"]
platforms = ["linux-64-cuda", "osx-arm64"]
```

--------------------------------

### Configure conda-pypi-map settings

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Examples for disabling PyPI mapping globally or for specific channels.

```toml
# or
conda-pypi-map = { conda-forge = false }    # disable for one channel
```

--------------------------------

### Define basic package constraints

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Use the [constraints] table to restrict versions of transitive dependencies without forcing their installation.

```toml
# openssl will be pulled in transitively; this constraint
# ensures we never end up with a vulnerable 1.x release.
requests = ">=2.28"

[constraints]
openssl = ">=3.0"
```

```toml
[constraints]
openssl = { channel = "conda-forge", version = ">=3.0" }
```

--------------------------------

### Example pixi.toml manifest

Source: https://pixi.prefix.dev/latest/first_workspace

The initial configuration file created by pixi init.

```toml
[workspace]
authors = ["Jane Doe <jane.doe@example.com>"]
channels = ["conda-forge"]
name = "my_workspace"
platforms = ["osx-arm64"]
version = "0.1.0"

[tasks]

[dependencies]
```

--------------------------------

### Define run constraints

Source: https://pixi.prefix.dev/latest/reference/pixi_manifest

Apply version constraints to packages in the run environment without forcing their installation.

```toml
[package.run-constraints]
numpy = ">=2"
```

--------------------------------

### Set workspace name example

Source: https://pixi.prefix.dev/latest/reference/cli/pixi/workspace/name/set

Example command to set the workspace name to 'my-workspace'.

```bash
pixi workspace name set "my-workspace"
```

--------------------------------

### Example project layout for combined binary/library

Source: https://pixi.prefix.dev/latest/build/backends/pixi-build-mojo

Visual representation of a project structure containing both a binary and a library package.

```text
.
├── greetings
│   ├── __init__.mojo
│   └── lib.mojo
├── main.mojo
├── pixi.lock
├── pixi.toml
└── README.md
```

--------------------------------

### Setup Pixi in GitHub Actions

Source: https://pixi.prefix.dev/latest/switching_from/uv

Use the official setup-pixi action to configure the environment in CI.

```yaml
- uses: prefix-dev/setup-pixi@v0.8.8
```

--------------------------------

### Force Architecture Installation (Linux/macOS)

Source: https://pixi.prefix.dev/latest/installation

Forces the installation of a specific architecture, such as x86_64 on Apple Silicon.

```bash
curl -fsSL https://pixi.sh/install.sh | PIXI_ARCH=x86_64 bash
```

--------------------------------

### Install Starship globally

Source: https://pixi.prefix.dev/latest/integration/third_party/starship

Use this command to install the Starship prompt globally via Pixi.

```bash
pixi global install starship
```

--------------------------------

### Install Global Package for Specific Platform

Source: https://pixi.prefix.dev/latest/global_tools/introduction

Installs a package targeting a specific platform architecture.

```bash
pixi global install --platform osx-64 python
```

--------------------------------

### Install direnv globally

Source: https://pixi.prefix.dev/latest/integration/third_party/direnv

Use the Pixi global install command to add direnv to your environment.

```bash
pixi global install direnv
```

--------------------------------

### Initialize Pixi with a new pyproject.toml

Source: https://pixi.prefix.dev/latest/python/pyproject_toml

Use this command to create a new pyproject.toml manifest file from scratch with default Pixi settings.

```bash
pixi init --format pyproject
```

--------------------------------

### Run pixi-install-to-prefix with pixi exec

Source: https://pixi.prefix.dev/latest/integration/extensions/pixi_install_to_prefix

Execute the tool in a temporary environment without a permanent global installation.

```bash
pixi exec pixi-install-to-prefix ./my-environment
```

--------------------------------

### Install Global Tools with Pixi

Source: https://pixi.prefix.dev/latest

Install multiple command-line tools globally in an isolated manner.

```bash
pixi global install gh nvim ipython btop ripgrep
```

--------------------------------

### Example pyproject.toml configuration

Source: https://pixi.prefix.dev/latest/build/backends/pixi-build-python

A sample pyproject.toml file demonstrating how dependencies and build-system requirements are defined for the backend to process.

```toml
[project]
name = "my-package"
version = "1.0.0"
dependencies = [
    "requests>=2.28",
    "pydantic>=2.0,<3.0",
]

[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
```

--------------------------------

### Initialize and run a ROS 2 Humble workspace

Source: https://pixi.prefix.dev/latest/robotics

Commands to initialize a new Pixi project with RoboStack channels, add ROS desktop dependencies, and launch RViz2.

```bash
pixi init my_ros_ws -c https://prefix.dev/robostack-humble -c https://prefix.dev/conda-forge
cd my_ros_ws
pixi add ros-humble-desktop
pixi run rviz2
```

--------------------------------

### Initialize Pixi Project

Source: https://pixi.prefix.dev/latest/build/python

Command to initialize a new Pixi project using the pixi format.

```bash
pixi init --format pixi
```
Tokens:
Raw