@@ -101,6 +101,13 @@ If `ide_product_code` and `ide_build_number` is missing, Toolbox will only open
101101page. Coder Toolbox will attempt to start the workspace if it’s not already running; however, for the most reliable
102102experience, it’s recommended to ensure the workspace is running prior to initiating the connection.
103103
104+ > ⚠️ Note: ` folder ` should point to a remote IDEA project that has already been opened and appears in the ` Projects `
105+ > tab.
106+ > If the path refers to a project that doesn't exist, the remote IDE won’t start or load it.
107+
108+ > Until [ TBX-14952] ( https://youtrack.jetbrains.com/issue/TBX-14952/ ) is fixed, it's best to either use a path to a
109+ > previously opened project or leave it empty.
110+
104111## Configuring and Testing workspace polling with HTTP & SOCKS5 Proxy
105112
106113This section explains how to set up a local proxy (without authentication which is not yet supported) and verify that
@@ -139,11 +146,11 @@ mitmproxy can do HTTP and SOCKS5 proxying. To configure one or the other:
139146
140147## Debugging and Reporting issues
141148
142- Enabling debug logging is essential for diagnosing issues with the Toolbox plugin, especially when SSH
143- connections to the remote environment fail — it provides detailed output that includes SSH negotiation
149+ Enabling debug logging is essential for diagnosing issues with the Toolbox plugin, especially when SSH
150+ connections to the remote environment fail — it provides detailed output that includes SSH negotiation
144151and command execution, which is not visible at the default log level.
145152
146- If you encounter a problem with Coder's JetBrains Toolbox plugin, follow the steps below to gather more
153+ If you encounter a problem with Coder's JetBrains Toolbox plugin, follow the steps below to gather more
147154information and help us diagnose and resolve it quickly.
148155
149156### Enable Debug Logging
@@ -159,46 +166,48 @@ Steps to enable debug logging:
159166
1601673 . In the screen that appears, select _ DEBUG_ for the ` Log level: ` section.
161168
162- 4 . Hit the back button at the top.
169+ 4 . Hit the back button at the top.
163170
164171There is no need to restart Toolbox, as it will begin logging at the __ DEBUG__ level right away.
165172
166173> ⚠️ ** Attention:** Toolbox does not persist log level configuration between restarts.
167174
168175#### Viewing the Logs
169176
170- Once enabled, debug logs will be written to the Toolbox log files. You can access logs directly
177+ Once enabled, debug logs will be written to the Toolbox log files. You can access logs directly
171178via Toolbox App Menu > About > Show log files.
172179
173- Alternatively, you can generate a ZIP file using the Workspace action menu, available either on the main
180+ Alternatively, you can generate a ZIP file using the Workspace action menu, available either on the main
174181Workspaces page in Coder or within the individual workspace view, under the option labeled _ Collect logs_ .
175182
176183## Coder Settings
177184
178185The Coder Settings allows users to control CLI download behavior, SSH configuration, TLS parameters, and data
179186storage paths. The options can be configured from the plugin's main Workspaces page > deployment action menu > Settings.
180187
181- ### CLI related settings
188+ ### CLI related settings
182189
183190``` Binary source ``` specifies the source URL or relative path from which the Coder CLI should be downloaded.
184191If a relative path is provided, it is resolved against the deployment domain.
185192
186193``` Enable downloads ``` allows automatic downloading of the CLI if the current version is missing or outdated.
187194
188- ``` Binary directory ``` specifies the directory where CLI binaries are stored. If omitted, it defaults to the data directory.
195+ ``` Binary directory ``` specifies the directory where CLI binaries are stored. If omitted, it defaults to the data
196+ directory.
189197
190198``` Enable binary directory fallback ``` if enabled, falls back to the data directory when the specified binary
191199directory is not writable.
192200
193- ``` Data directory ``` directory where plugin-specific data such as session tokens and binaries are stored if not
201+ ``` Data directory ``` directory where plugin-specific data such as session tokens and binaries are stored if not
194202overridden by the binary directory setting.
195203
196204``` Header command ``` command that outputs additional HTTP headers. Each line of output must be in the format key=value.
197205The environment variable CODER_URL will be available to the command process.
198206
199207### TLS settings
200208
201- The following options control the secure communication behavior of the plugin with Coder deployment and its available API.
209+ The following options control the secure communication behavior of the plugin with Coder deployment and its available
210+ API.
202211
203212``` TLS cert path ``` path to a client certificate file for TLS authentication with Coder deployment.
204213The certificate should be in X.509 PEM format.
@@ -210,7 +219,7 @@ The certificate should be in X.509 PEM format.
210219certs returned by the Coder deployment. The file should be in X.509 PEM format. This option can also be used to verify
211220proxy certificates.
212221
213- ``` TLS alternate hostname ``` overrides the hostname used in TLS verification. This is useful when the hostname
222+ ``` TLS alternate hostname ``` overrides the hostname used in TLS verification. This is useful when the hostname
214223used to connect to the Coder deployment does not match the hostname in the TLS certificate.
215224
216225### SSH settings
@@ -227,11 +236,13 @@ rules for matching multiple workspaces.
227236
228237``` SSH network metrics directory ``` directory where network information used by the SSH proxy is stored.
229238
230- ``` Extra SSH options ``` additional options appended to the SSH configuration. Can be used to customize the behavior of SSH connections.
239+ ``` Extra SSH options ``` additional options appended to the SSH configuration. Can be used to customize the behavior of
240+ SSH connections.
231241
232242### Saving Changes
233243
234- Changes made in the settings page are saved by clicking the Save button. Some changes, like toggling SSH wildcard support,
244+ Changes made in the settings page are saved by clicking the Save button. Some changes, like toggling SSH wildcard
245+ support,
235246may trigger regeneration of SSH configurations.
236247
237248### Security considerations
0 commit comments