Run Configurations
A run configuration is a saved command: which tool, which project, which action and with which options. You pick one in the title bar and press Run; Genexy opens a terminal tab for it in the Terminal panel and runs it there. Run configurations are free and need no account.
Run, stop, debug
The selector sits in the title bar, to the right of the project search. Next to it:
- Run (the green triangle) starts the selected configuration. While it runs the button becomes Stop, and the configuration shows a pulsing green dot in the list.
- Debug (the bug) starts the same configuration under the debugger. It appears for Go, Maven and Gradle configurations; see Debugging.
Output goes to a terminal tab named after the configuration. Closing that tab stops the run, and pressing Run again runs it once more. A configuration can also Start automatically when the project opens.
On Android and iOS the Run button is disabled with the tooltip “Commands cannot run on mobile”: the operating system does not let the app start the processes a build needs. Connect to a desktop through Remote Access to run from a phone or tablet.
Tools
Genexy scans the project for manifests and offers the projects it finds for each tool, including nested projects in subfolders. A configuration from a nested project carries that folder as a badge.
| Tool | Chip | Detected from | Actions |
|---|---|---|---|
| Maven | mvn | pom.xml (and mvnw) | run (spring-boot:run), dev (quarkus:dev), build, test, … |
| Gradle | gr | build.gradle(.kts) (and gradlew) | run (bootRun), build, test, clean build, assemble, check |
| Go | go | go.mod | run, build, test, bench, vet, generate, tidy |
| Node / TypeScript | TS | package.json | any script from package.json |
| C# / .NET | C# | *.csproj | run, watch, build, test, publish, restore, clean |
| Python | py | pyproject.toml | Django, uvicorn, Flask, file, module, pytest, … |
| Rust / Cargo | rs | Cargo.toml | run, build, test, check, clippy, bench, fmt |
| PHP / Composer | php | composer.json | serve, test (PHPUnit or artisan), migrate, install, update |
| Ruby / Bundler | rb | Gemfile | server, console, migrate (Rails), test, install |
| Swift, Dart, Flutter | sw, dt, fl | Package.swift, pubspec.yaml | run, build, test, … |
| C / C++ (CMake) | C++ | CMakeLists.txt | configure, build, test (ctest), run executable, clean |
| Make | mk | Makefile | any target from the Makefile |
| Docker Compose | dc | compose.yaml | up, down, build, logs, restart, pull, ps |
| Genexy Regenerate | gx | .genexy/component.yaml | regenerate a generated component, dry run, force |
| Single file | {} | any file | run a script with its interpreter |
| Command | >_ | – | any command line |
Framework actions only appear where the project actually uses the framework: Maven’s run needs Spring Boot, dev needs Quarkus, and the Python actions follow Django, FastAPI or Flask.
Edit configurations
Edit Configurations… at the bottom of the list opens the editor. The left column lists the configurations, with Duplicate and + (add); the right side edits the selected one.
- Name is suggested as
component [ACTION], for exampleland-routing [RUN], until you rename it. - Tool, Project and Action come from what the scan detected; the hint shows how many projects were found.
- Options are form fields: Skip tests, Maven profiles, Spring profile,
-race,-tags, the .NET configuration and so on, depending on the tool. Use the project wrapper (mvnw/gradlew) runs the wrapper instead of a global installation. - Arguments, Working directory, Shell (default for the platform, or a specific one including Genexy Shell), Env file and Environment variables. Variables are exported after the env file, so they override it.
- The debug section configures how the debugger attaches; see Debugging.
- Will run in terminal previews the exact command. If something is missing, the preview says what.
Where they are stored
Configurations are saved with the project or with a component, so they can be committed and shared with the team. Stored in in the editor chooses where:
- Project: the project’s
.genexy/project.yaml, for scripts and tools of the whole project (compose files, a docs site). - Component: the component’s
.genexy/component.yaml, with the working directory relative to the component’s folder. The configuration travels with the component: it is there when someone opens only that component, or the component in another project. A new configuration whose working directory is inside a component is stored with that component.
The Run selector marks a component’s configurations with its name. Configurations of a nested project are saved in that
project’s own project.yaml. Which configuration is selected is a
personal preference and is not written to the project.
From AI
Your AI can read and save run configurations through the Genexy MCP tools, and start them under the debugger with the debug tools. See AI Chat.