Where a PACKAGED install puts the site — openmixer-manual's payload, beside the surface
the same RPM set already ships at %{_datadir}/openmixer/web-ui, so there is one obvious
location rather than a per-host choice.
This is a DERIVED default, not configuration. A parameter the system can work out must
not be something an operator remembers: the rig ran with a hand-set OPENMIXER_MANUAL_DIR
pointing one level into a dev build tree, and nothing noticed, precisely because there was
no working default to fall back to.
Where a PACKAGED install puts the site —
openmixer-manual's payload, beside the surface the same RPM set already ships at%{_datadir}/openmixer/web-ui, so there is one obvious location rather than a per-host choice.This is a DERIVED default, not configuration. A parameter the system can work out must not be something an operator remembers: the rig ran with a hand-set
OPENMIXER_MANUAL_DIRpointing one level into a dev build tree, and nothing noticed, precisely because there was no working default to fall back to.