It is important to note that this environment is being built up from multiple places, and ***not all variables are overridable***. For a complete listing checkout the [full build environment documentation](rtcds-Build-Environment-Variables)
<details>
<summary>Production Build Server Environment Example</summary>
```shell
(diskless)controls@h1build:~$ rtcds env
found host specific environment file '/etc/advligorts/systemd_env_h1build'
In order for `rtcds` to find your model (the <model_name>.mdl file) the `RCG_LIB_PATH` env variable needs to have a path to the directory containing it. The best way to do that, is adding the directory path to the `RCG_LIB_PATH` line in the `/etc/advligorts/env` file.
If you have your custom model located at `/home/controls/models/` then you should add that path (colon (:) separated) to your env file.
After adding the line, your `/etc/advligorts/env` file might look like:
Note the `RTS_ENV` environmental variable will override where `rtcds` looks for the env file, so if you want the default functionality make sure it is unset.
### Verification
You can list your `rtcds` environment again with the `rtcds env` command and your output after setting the version/src/build variables and editing the `/etc/advligorts/env` file will look something like:
While `rtcds` has appended some additional paths to the `RCG_LIB_PATH` variable, the path we added (`/home/controls/models/`) is present in the list. Now when we run `rtcds build <model_name>`, `rtcds` will look in `/home/controls/models/` for a file named `<model_name>.mdl`
