render+deploy: align latex gate with api, non-root api image #22
Loading…
Reference in a new issue
No description provided.
Delete branch "integrator/lane-followups"
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?
What
Lane-followup round for #20 (my lanes: render + deploy):
RGXR_LATEX_ENABLEDparsing was a denylist (enabled unless0/false/no/off) while the api gate is an allowlist (true/1/yes/on); render now mirrors the api'sparse_flagexactly, so both gates share one truthy set (the api gate evaluates first; this removes the divergence class entirely). No api changes needed.useradd rgxr (uid 1000)+chown+USER rgxr; render scratch lives in/tmp, 8080 unprivileged. Verified live in the built image:id→ uid 1000, healthz ok, fast render returns SVG, full latex pipeline (dot2tex → pdflatex → dvisvgm 3.0.3) returns SVG as non-root.Gates
cargo fmt --check,cargo clippy --workspace --all-targetsclean.cargo test --workspace: 96 passed, 0 failed (44 core + 28 core-acceptance + 11 api + 13 render).docker build -f deploy/api.Dockerfilegreen + live non-root verification above.Review clarifications (both non-blocking):
y,enabled, any junk) now disable it — the one thing a deployer scanning env diffs could trip on. The contract table only pinsfalse→ disabled + default false, which the allowlist satisfies.f1cef9caddedrgxr-renderto the api package deps without committing the lockfile row; this PR commits it.