Run/Debug Configuration: Shell Script
Use this dialog to configure running shell scripts. For details on working with shell scripts in JetBrains Rider, see Shell scripts.
The set of parameters in the dialog depends on the option you select under Execute:
Script file (a configuration to run a script file)
Script text (a configuration to run a single command)
Provide the path to the shell script file. Type the path manually or click and select the path in the dialog that opens.
Specify the options that you want to pass to the script when it is launched.
Provide the absolute path of a directory to run the script in.
Specify environment variables if you need them in the script. You can click to open the Environment Variables window where you can browse and copy existing variables or create your own.
Provide the path to the interpreter for running the script. Type the path manually or click and select the path in the dialog that opens.
Specify the options that you want to pass to the script interpreter.
Enter the text of the command to be run.
Provide the absolute path of a directory to run the command in.
Specify environment variables if you need them in the command. You can click to open the Environment Variables window where you can browse and copy existing variables or create your own.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow parallel run
Allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, JetBrains Rider suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file
Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.
By default, it is disabled, and JetBrains Rider stores run configuration settings in .idea/workspace.xml.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your solution as well as adjust default configurations templates.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.
Show this page
Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5.