RubyMine Deployment Configurations vs. Remote Application Log Tailing: Integration Gap

Integration Boundary

RubyMine separates deployment operations (SFTP, FTPS, Docker) from post-deploy application diagnostics. The Deployment tool window records file-transfer events, while container logs appear only in the Run tool window when a Docker run configuration is used—not when a Docker deployment configuration pushes images. For traditional SFTP/FTPS deployments, no application-level log stream is surfaced at all.

Unresolved Behavior

The "Show deployment logs" checkbox in a deployment configuration controls visibility of the transfer log. It is unclear whether this setting is intended to also tail a remote application log file (e.g., log/production.log) after synchronization completes. JetBrains documentation does not specify such coupling, and the UI provides no target-log-path field. Version differences (2023.x vs 2024.x) may affect whether any automatic tailing occurs.

Constraints

Remote log tailing requires an active SSH session, correct file permissions, and a known log path—none of which the deployment configuration currently captures. Docker daemon settings and run-configuration flags further isolate container logs from deployment configurations.

Does the "Show deployment logs" option have a documented or planned scope that includes remote application log tailing? Is there a supported extension point to bind a deployment configuration to a specific remote log file? How should a workflow correlate a successful SFTP sync with subsequent Rails error entries without leaving the IDE?