7c1745325e
Build and Publish Site / docker (push) Successful in 3s
Update user docs Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01A9GjKvXCmfgJpKzbQdZ7UA Co-authored-by: Benjamin Labrecque <labrecque.benji@gmail.com> Reviewed-on: #74
31 lines
918 B
Markdown
31 lines
918 B
Markdown
# GUI
|
|
|
|
## Launch
|
|
|
|
```
|
|
cd <repo-root>
|
|
```
|
|
|
|
In `prod`:
|
|
```
|
|
./bin/sls_hla_launch_gui.sh qt/A_BD_InjectionGuard.ui
|
|
```
|
|
|
|
In `dev`:
|
|
```
|
|
./bin/sls_hla_launch_gui.sh qt/A_BD_InjectionGuard.ui dev
|
|
```
|
|
|
|
Any extra arguments are passed straight through to `caqtdm`, e.g. to set a macro:
|
|
|
|
```
|
|
./bin/sls_hla_launch_gui.sh qt/A_BD_Tune.ui dev -macro "OTHER_ENV_VAR=HEYHEY"
|
|
```
|
|
|
|
**Note:** launching straight from a git checkout, as above, uses the raw `.ui` files as
|
|
committed - including the literal `{{ agebd_env_suffix_upper }}`/`{{ agebd_env_suffix_lower }}`
|
|
placeholders in their PV names. Those only get substituted with `-DEV`/`-dev` (or emptied out,
|
|
in `prod`) at deploy time, by `.gitea/workflows/deploy.yml`'s `"Qt - deploy"` step, on the
|
|
*deployed* copy at `/sls/bd/hla/<env>/qt/`. If widgets show up blank or unresponsive, check
|
|
whether you're accidentally pointing at the raw checkout instead of the deployed `.ui` file.
|