feat: install an environment of a lockfile to a target dir #3953
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature makes pixi to install an environment without a workspace and global/exec specs. This can help distribute and setup many complex and reproducible environments fast based on the
pixi
/conda
/uv
caches.The new command
pixi deploy
reads the all the required information for installing a single environment from a specified.lock
file and global/cli configs, and do not try to search a workspace manifest. Another required option is the target prefix folder to install to. The install steps are similar topixi install
command, except that the.lock
file will not be updated to the manifest. The conda and pypi packages are both updated to the prefix folder, except some limit on the source packages.Another new subcommand
pixi workspace export split-lockfile
splits thepixi.lock
of the current workspace into a specified base folder. The packages of each environment and platform are written into<target>/{platform}/{environment}.lock
.