README.md

Sub-package for pixi installation

This sub-package installs pixi into a layer and makes it available on the PATH.

Integration

The pixi CNB provides pixi as a dependency. Downstream buildpacks can require the pixi dependency by generating a Build Plan TOML file that looks like the following:

[[requires]]

  # The name of the Uv dependency is "pixi". This value is considered
  # part of the public API for the buildpack and will not change without a plan
  # for deprecation.
  name = "pixi"

  # The version of the pixi dependency is not required. In the case it
  # is not specified, the buildpack will provide the default version, which can
  # be seen in the buildpack.toml file.
  # If you wish to request a specific version, the buildpack supports
  # specifying a semver constraint in the form of "0.*", "0.9.*", or even
  # "0.9.22".
  version = "0.9.22"

  # The Miniconda buildpack supports some non-required metadata options.
  [requires.metadata]

    # Setting the build flag to true will ensure that the pixi
    # dependency is available on the $PATH for subsequent buildpacks during
    # their build phase. If you are writing a buildpack that needs to run
    # pixi during its build process, this flag should be set to true.
    build = true

    # Setting the launch flag to true will ensure that the pixi
    # dependency is available on the $PATH for the running application. If you are
    # writing an application that needs to run pixi at runtime, this flag
    # should be set to true.
    launch = true