Limits of Deployment Log Visibility: Remote Script Errors

Direct Answer

No, WebStorm does not provide a configuration to pipe the stdout or stderr of a remote deployment script into the Deployment Log panel. The Deployment Log is designed to track the IDE's internal transfer events (SSH handshakes, file uploads, and deletions) rather than the execution output of processes running on the remote server. Consequently, the exit code of a remote process is also not exposed in this view.

Likely Explanation

The Deployment Log operates at the transport layer. When WebStorm triggers a remote script (such as a post-upload command), it typically executes the command via a non-interactive shell session. Because the IDE is monitoring the transfer status and not maintaining a persistent interactive terminal session for that specific task, the remote process's output stream is not captured or routed back to the UI panel.

Recommended Workarounds

Since the output is not available in the IDE UI, you must persist the data on the remote server or change how the script is executed.

Option 1: Remote Log Redirection (Best for Automated Deployments)

Modify your remote deployment script to redirect all output and the exit status to a file. You can then view this file using the WebStorm Remote Host tool window.

# Example: Redirect stdout and stderr to a log file and save the exit code
./deploy_script.sh > /tmp/deploy.log 2>&1
echo $? > /tmp/deploy_exit_code

After the deployment fails, right-click /tmp/deploy.log in the Remote Host view and select Download from Here to inspect the error.

Option 2: Use a Run Configuration (Best for Debugging)

If you need real-time visibility into the script's execution and its exit code, do not rely on the Deployment automation. Instead:

1. Go to Run | Edit Configurations.
2. Create a new SSH Session configuration.
3. Specify the command to run your deployment script.
4. Execute this configuration. The output and exit code will appear in the Run tool window, which supports full stdout/stderr capture.

Verification Steps

• Confirming the Gap: Create a dummy script that prints "Hello World" and exits with exit 1. Run it via the deployment settings and verify that neither the string nor the code 1 appears in the Deployment Log.
• Validating Redirection: Use the redirection method above and verify that /tmp/deploy_exit_code contains 1.

Missing Detail: Is the remote script triggered by a WebStorm "After upload" action, or is it a server-side hook (like a git hook) triggered by the file arrival? If it is a server-side hook, the IDE has no connection to the process whatsoever, making Option 1 the only viable solution.