# Configuration and environment

## Committed absolute paths pin the build to this box [#690] {#paths}

Costs: `go.mod` replaces Hexis with `/home/kami/apps/hexis`, `start-maven.sh`
hardcodes the checkout and the data directory, and `deploy/mavgpud.json` holds
workstation model and Python paths. Vendoring hides the `go.mod` problem for an
ordinary build. `-mod=mod`, `go mod tidy` and a fresh checkout all fail.
Revisit when: anyone clones this repo elsewhere, or a `tidy` is needed.
Workaround: build only from this checkout, with the vendor directory.

## The env example omits deployed variables [#691] {#secrets}

Costs: a fresh deploy can lose remote speech-to-text or ambient authentication
and run on fallback behaviour with an apparently valid config. Three variables
are referenced and undocumented: `MAVEN_STT_TOKEN`, `MAVEN_AMBIENT_TOKEN` and
`CW2_TOKEN`. V-673 added `MAVEN_GPU_TOKEN` to the example.
It is not silent. The loader logs which variables were unset and says whatever
they configure is off. What is missing is a startup failure.
Revisit when: the box is redeployed from scratch, or a new secret is added.
Workaround: read that log line at startup.
