Conversation
Extract uvx binary from the uv release archive alongside uv, create bin/uvx wrappers/symlinks, export $REDMATTER_UVX via env.sh/env.ps1/env.bat, and record uvx_env in the installed distro.toml. Update README and TESTING docs.
…refix Callers can now pass --env-prefix REDMATTER instead of spelling out --uv-env REDMATTER_UV --uvx-env REDMATTER_UVX --python-env REDMATTER_PYTHON. The two styles are mutually exclusive; mixing them or omitting both produces a clear error. Existing invocations using the individual flags are unchanged.
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
| Infrastructure as Code | View in Orca | ||
| SAST | View in Orca | ||
| Secrets | View in Orca | ||
| Vulnerabilities | View in Orca |
PR Review:
|
|
All addressed:
|
…DME env-prefix examples
Summary
--env-prefixoption (setup.py,install.ps1): callers can now pass a single prefix (e.g.REDMATTER) instead of spelling out all three env var names individually. The prefix derives{PREFIX}_UV,{PREFIX}_UVX, and{PREFIX}_PYTHONautomatically.--env-prefixwith any of--uv-env/--uvx-env/--python-enverrors with a clear message; omitting both also errors. Existing invocations using explicit flags are unchanged.install.ps1): added-EnvPrefixparameter with matching validation;$setupArgsconstruction branches on which style is used.env.shon Windows (install.ps1): generatesenv.shfor Git Bash compatibility alongsideenv.ps1.Test plan
bash install.sh --prefix /tmp/test-mp --python 3.10 --env-prefix REDMATTER— succeeds; generatedenv.shexportsREDMATTER_UV,REDMATTER_UVX,REDMATTER_PYTHONbash install.sh --prefix /tmp/test-mp --python 3.10 --uv-env FOO_UV --uvx-env FOO_UVX --python-env FOO_PY— succeeds as beforebash install.sh --prefix /tmp/test-mp --python 3.10 --env-prefix REDMATTER --uv-env CUSTOM— errors with clear messagebash install.sh --prefix /tmp/test-mp --python 3.10— errors, prompts to use--env-prefixor individual flags