Development

Configuration

Launcher name, backend catalog URLs and other configuration parameters are baked in at compile time by crates/build-config. The build reads build.env from the repository root automatically (environment variables take priority when set). If you change config values, rebuild the launcher.

If you are not using build.env, export the variables yourself before building. See the Launcher configuration page for the full list.

Building

The launcher can be built like any other Rust project

If you aren't familiar with Rust tooling, start by installing rustup from rustup.rs. Then, use cargo run --bin launcher to build and run the launcher in debug configuration, or cargo build --bin launcher --release to create a release binary

To run the full backend stack locally, use docker compose -f docker-compose-dev.yml up from the repository root.