fix: omit empty frontend directory from compose #85
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/v235-compose-default"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The default Compose file exported
PORTAL_FRONTEND_DIR=. Clap treats the empty environment value forOption<PathBuf>as a supplied option without a value, so the referencedocker compose uppath could fail before the built-in landing-page fallback starts.Fix
Validation
cargo fmt --checkcargo test --locked: 144 passed, 3 ignoredcargo clippy --locked --workspace --all-targets --all-features -- -D warningsdocker compose config:PORTAL_FRONTEND_DIRomitteddocker compose up --build: container running, HTTPS 200, built-in HTML servedThis is a port patch on top of upstream v2.3.5; no wire/API behavior changes.
Released as
v2.3.5+rs.2.Validation summary:
-D warningspassed.sha256:2ba2b60987b67b282ddeea2612d8931130b68a4de479d6c64f048518ea70fbc4.portal-relay v2.3.5+rs.2; 8/8 expose services are active and public endpoint gates pass.Infrastructure note: the first PR CI attempt was assigned to a Docker runner incorrectly advertising
rust-hostand failed atrustup: command not found. The conflicting label was removed; the unchanged source tree then passed on the approved Rust host runner.