Create Flame IDE Run Configurations for scripts, shell commands, browser URLs, tests, and HTTP requests, with project or group scope and environment sources.
Run Configurations in Flame IDE. Select the image to enlarge.
WHY IT HELPS
Keep the next decision in context.
Opening a project should not require remembering which three terminals, environment files, and browser URLs you used yesterday. A Flame Run Configuration is a named set of launch actions with a working directory and environment. Keep separate recipes for a frontend, API, or full development session, and share common recipes through project groups.
Combine the actions you already use
Launch package scripts, shell commands, files, internal or external browser URLs, test watchers, and HTTP requests from one saved configuration.
Choose the scope once
Save a configuration in Project Settings for one repository or Group Settings for member projects. Inherited group recipes execute in each member project's own directory.
Keep configuration separate from secrets
Resolve environment values from literal variables and supported file, command, or API sources. Portable exports scrub credentials and environment maps; configure sensitive values locally.
HOW TO USE IT
A practical starting point.
Create a named configuration
Open Project Settings → Run configurations, or the same section in Group Settings. Add a recipe such as Frontend or API, expand it, and choose its working directory.
Add the start actions
Use Add action to choose package scripts, terminal commands, browser URLs, files, test watch, or HTTP requests. Enter the command or target for each enabled action. A typical frontend recipe runs the dev script and opens its local URL.
Set environment and cleanup
Configure the required variables and environment sources. Add session-stop shell commands, package scripts, or HTTP requests only when appropriate. Teardown requests and commands have bounded execution time.
Run and inspect the session
Use Run, Stop, or Restart from the configuration or project controls. Flame reconciles matching terminal and browser actions when you run again. HTTP request actions intentionally send a new request each time.
REQUIREMENTS & LIMITS
Know what the tool depends on.
A saved launch sequence is not a guarantee that a service is healthy or ready. Inspect the terminal and add explicit readiness logic to your commands when the next step depends on it.
Inherited group recipes execute in member projects; they are not automatically a broadcast to every repository. Use Broadcast Terminal when you want command fan-out.
Environment commands and HTTP actions execute real work. Repeated HTTP actions may repeat side effects, even when other launch actions are reused.
FAQ
Run Configurations: common questions
Starting a configuration reconciles supported enabled actions, reusing matching active terminals and browser tabs. HTTP request actions are the exception and run on every invocation.
Yes. Group configurations are inherited by member projects and execute in the member's directory. Project configuration can remain specific to an individual repository.
Configurations support session-stop terminal commands, package scripts, and HTTP requests. Choose cleanup deliberately, particularly for shared services and containers.