Command-line interface

The installation directory contains batch scripts and executables for launching DataGrip, formatting the source code, and running inspections. To use them from the Command Prompt cmd.exe, add the location of the DataGrip bin folder to the PATH environment variable. For example, if you installed DataGrip to C:\Program Files\JetBrains\DataGrip, you can use the following command:

This command changes the PATH environment variable for the current shell only (the current instance of cmd.exe). If you want to update it permanently for the current user, run setx:

To update it system-wide for all users, run setx /M instead of setx.

After you configure the PATH variable, you can run the executable from any working directory in the Command Prompt: datagrip64.exe. Alternatively, you can use the batch script: datagrip.bat.

To run DataGrip from the shell, use the open command with the following options:

• -a: specify the application.

• --args: specify additional arguments when passing more than just the file or directory to open.

• -n: open a new instance of the application even if one is already running.

For example, you can run DataGrip.app with the following command:

You can create a shell script with this command in a directory from your PATH environment variable. For example, create the file /usr/local/bin/datagrip with the following contents:

Make sure you have permissions to execute the script and since /usr/local/bin should be in the PATH environment variable by default, you should be able to run datagrip from anywhere in the shell.

On Linux, the installation directory contains the launcher shell script datagrip.sh under bin. For example, if you installed DataGrip to /opt/datagrip, you can run the script using the following command:

You can create a symbolic link to the launcher script in a directory from the PATH environment variable. For example, if you installed DataGrip to /opt/datagrip and want to create a link named datagrip in /usr/local/bin, run the following command:

Since /usr/local/bin should be in the PATH environment variable by default, you should be able to run the datagrip command from anywhere in the shell.

By default, the Toolbox App puts shell scripts in a directory from the system PATH environment variable, so you can run the name of the script as a command to launch DataGrip from any working directory.

Rename shell scripts

If you have several versions of the same IDE, the Toolbox App generates a shell script for each version with a unique name. You can change the name of the shell script for an IDE instance in the settings for this specific instance.

1. Open the Toolbox App.

2. Click next to an IDE instance and select Settings.

3. At the bottom of the Configuration section, change the Shell script name field.

or

By default, the Toolbox App puts shell scripts in a directory from the system PATH environment variable, so you can run the name of the script as a command to launch DataGrip from any working directory.

Rename shell scripts

If you have several versions of the same IDE, the Toolbox App generates a shell script for each version with a unique name. You can change the name of the shell script for an IDE instance in the settings for this specific instance.

1. Open the Toolbox App.

2. Click next to an IDE instance and select Settings.

3. At the bottom of the Configuration section, change the Shell script name field.

By default, the Toolbox App puts shell scripts in a directory from the system PATH environment variable, so you can run the name of the script as a command to launch DataGrip from any working directory.

Rename shell scripts

If you have several versions of the same IDE, the Toolbox App generates a shell script for each version with a unique name. You can change the name of the shell script for an IDE instance in the settings for this specific instance.

1. Open the Toolbox App.

2. Click next to an IDE instance and select Settings.

3. At the bottom of the Configuration section, change the Shell script name field.