aare_launcher

CLI/TUI launcher for the AareDAQ server and GUI on MX beamline consoles at PSI.

Installed as the aarel command. It detects the current beamline and launches the matching application, opens a TUI to pick one, or deploys a new checkout.

Usage

aarel pick          # open the TUI to choose what to launch
aarel gui           # launch the GUI for the detected beamline
aarel server        # launch the server for the detected beamline

Each command has a single-letter alias (p, g, s). --config <path> selects a different config file; it defaults to /etc/aarel/defaults.json.

Launching

gui and server default to the deployment for the detected beamline. Pass -d/--deployment <name> to launch a specific one:

aarel gui -d x10sa                      # launch the x10sa GUI
aarel server -d mytest                  # launch a custom deployment's server
aarel server --deployment x06da --env-file ./dev.env

Deployments found under deployments_base are offered alongside the configured beamlines, so -d accepts either a configured beamline name or a discovered deployment.

Development

cargo build            # build
cargo test             # run the tests
cargo fmt --all        # format
cargo clippy --all-targets --all-features -- -D warnings   # lint

Releases are automated with semantic-release: merging a PR to main derives the next version from the commit history, bumps Cargo.toml, tags the release and builds the RPM.

Commit messages must follow Conventional Commits. The release version and notes are generated from them, so a commit that isn't feat:, fix:, etc. produces no release. Use feat: for a minor bump, fix: for a patch, and a feat!:/fix!: (or a BREAKING CHANGE: footer) for a major bump.