this is a follow up to a small issue I fixed here #318
Deploy only uses unit.command (run via sh -c). args and the env map never reach the app — env::vault works only because it separately triggers Locksmith.
Code: api/src/main.rs:2059 uses command only; BuildRequest has no args/env; build.rs:248 runs sh -c; run.sh.template emits no env.
Decision: is command a shell string or a bare binary?
- A: keep
sh -c, join args + emit env exports (back-compatible) - B: exec directly with argv + env (clean, but breaks
command = "FOO=1 /app")
> this is a follow up to a small issue I fixed here https://codeberg.org/caution/platform/pulls/318
Deploy only uses `unit.command` (run via `sh -c`). `args` and the `env` map never reach the app — `env::vault` works only because it separately triggers Locksmith.
Code: `api/src/main.rs:2059` uses `command` only; `BuildRequest` has no args/env; `build.rs:248` runs `sh -c`; `run.sh.template` emits no env.
Decision: is `command` a shell string or a bare binary?
- A: keep `sh -c`, join args + emit env exports (back-compatible)
- B: exec directly with argv + env (clean, but breaks `command = "FOO=1 /app"`)