Replies: 3 comments 1 reply
-
@ruben-arts @baszalmstra |
Beta Was this translation helpful? Give feedback.
-
Did you check out It feels like it comes really close to what you want to achieve |
Beta Was this translation helpful? Give feedback.
-
A POC of a unix installer for the lockfile, insert these lines at the beginning of a lockfile: #!/bin/sh
type : |
true installer header
echo Detect and install pixi to ~/.pixi/bin ...
exec target/pixi/debug/pixi deploy -l "$0" "$@" The header lines are both valid yaml block and posix shell, and also compatible to the rattler parser. Then run like this: ❯ ./runlock
Detect and install pixi to /root/.pixi/bin ...
error: the following required arguments were not provided:
<TARGET>
Usage: pixi deploy --lockfile <LOCKFILE> <TARGET>
For more information, try '--help'.
❯ ./runlock ./test-deploy/
Detect and install pixi to /root/.pixi/bin ...
❯ source test-deploy/bin/activate
❯ which python
/work/pixi/test-deploy/bin/python |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
Can we design a remote mode, in which we can:
environment_lock_file_hash
values, such as a TTL local cache, or httpHEAD
method on the lockfile url can response the updated hash, etc.With this function, the developers can easily share a run-time pixi env, or setup the env without cloning the full code repo.
Beta Was this translation helpful? Give feedback.
All reactions