You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user-guides/workspace-access/README.md
+79-45Lines changed: 79 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,35 +2,65 @@
2
2
3
3
There are many ways to connect to your workspace, the options are only limited by the template configuration.
4
4
5
-
> Deployment operators can learn more about different types of workspace connections and performance in our [networking docs](../admin/infrastructure/README.md).
5
+
> Deployment operators can learn more about different types of workspace connections and performance in our [networking docs](../../admin/infrastructure/README.md).
6
6
7
7
You can see the primary methods of connecting to your workspace in the workspace dashboard.
Coder Apps (from our [`coder_app`](https://registry.terraform.io/providers/coder/coder/latest/docs/resources/app) resource in terraform) provide IDE connections and the Terminal. Coder Apps can connect you to ports or run commands on the remote workspace. They be shared with other users by copying the URL from the button. Contact your template administrator if you have IDEs or tools you'd like added into your workspace.
14
16
15
17
, and can be extended with our [Module Registry](https://registry.coder.com/modules). -->
16
18
17
19
## Terminal
18
20
19
-
The terminal is enabled by implictily in Coder and allows you to access your workspace through a shell environment.
21
+
The terminal is implicitly enabled in Coder and allows you to access your workspace through the shell environment set by your template.
20
22
21
-
## Jetbrains IDEs
23
+
## SSH
22
24
23
-
We support Jetbrains IDEs using Gateway. Currently the following are supported:
24
-
- IntelliJ IDEA
25
-
- CLion
26
-
- GoLand
27
-
- PyCharm
28
-
- Rider
29
-
- RubyMine
30
-
- WebStorm
25
+
### Through with the CLI
31
26
32
-
Read our [docs on Jetbrains Gateway](./jetbrains-gateway.md) for more information on setup.
27
+
Coder will use the optimal path for an SSH connection (determined by your deployment's [networking configuration](../../admin/networking.md)) when using the CLI:
33
28
29
+
```console
30
+
coder ssh my-workspace
31
+
```
32
+
33
+
Or, you can configure plain SSH on your client below.
34
+
35
+
36
+
### Configure SSH
37
+
38
+
Coder generates [SSH key pairs](../../secrets.md#ssh-keys) for each user to simplify the setup process.
39
+
40
+
> Before proceeding, run `coder login <accessURL>` if you haven't already to
41
+
> authenticate the CLI with the web UI and your workspaces.
42
+
43
+
To access Coder via SSH, run the following in the terminal:
44
+
45
+
```console
46
+
coder config-ssh
47
+
```
48
+
49
+
> Run `coder config-ssh --dry-run` if you'd like to see the changes that will be
50
+
> made before proceeding.
51
+
52
+
Confirm that you want to continue by typing **yes** and pressing enter. If
53
+
successful, you'll see the following message:
54
+
55
+
```console
56
+
You should now be able to ssh into your workspace.
57
+
For example, try running:
58
+
59
+
$ ssh coder.<workspaceName>
60
+
```
61
+
62
+
Your workspace is now accessible via `ssh coder.<workspace_name>` (e.g.,
63
+
`ssh coder.myEnv` if your workspace is named `myEnv`).
34
64
35
65
## Visual Studio Code
36
66
@@ -47,6 +77,7 @@ on the `coder_agent` resource in your workspace template. See the
47
77
> The `VS Code Desktop` button can be hidden by enabling
Coder will use the optimal path for an SSH connection (determined by your deployment's [networking configuration](../admin/networking.md)) when using the CLI:
96
+
We support Jetbrains IDEs using [Gateway](https://www.jetbrains.com/remote-development/gateway/). The following IDEs are supported for remote development:
Read our [docs on Jetbrains Gateway](./jetbrains.md) for more information on connecting your Jetbrains IDEs.
71
107
72
-
Or, you can configure plain SSH on your client below.
73
108
109
+
## code-server
74
110
75
-
### Configure SSH
111
+
[code-server](https://github.com/coder/code-server) is our supported method of running
112
+
VS Code in the web browser. You can read more in our [documentation for code-server](https://coder.com/docs/code-server/latest).
76
113
77
-
Coder generates [SSH key pairs](../secrets.md#ssh-keys) for each user to simplify the setup process.
114
+

78
115
79
-
> Before proceeding, run `coder login <accessURL>` if you haven't already to
80
-
> authenticate the CLI with the web UI and your workspaces.
81
116
82
-
To access Coder via SSH, run the following in the terminal:
117
+
## Other Web IDEs
83
118
84
-
```console
85
-
coder config-ssh
86
-
```
119
+
<!-- TODO: update template guides link -->
87
120
88
-
> Run `coder config-ssh --dry-run` if you'd like to see the changes that will be
89
-
> made before proceeding.
121
+
We support a variety of other browser IDEs and tools to interact with your workspace. Each of these can be configured by your template admin using our [Web IDE guides](../../admin/templates/README.md).
90
122
91
-
Confirm that you want to continue by typing **yes** and pressing enter. If
92
-
successful, you'll see the following message:
123
+
Supported IDEs:
124
+
- VS Code Web
125
+
- JupyterLab
126
+
- RStudio
127
+
- Airflow
128
+
- File Browser
93
129
94
-
```console
95
-
You should now be able to ssh into your workspace.
96
-
For example, try running:
130
+
Our [Module Registry](https://registry.coder.com/modules) also hosts a variety of tools for extending the capability of your workspace. If you have a request for a new IDE or tool, please file an issue in our [Modules repo](https://github.com/coder/modules/issues).
97
131
98
-
$ ssh coder.<workspaceName>
99
-
```
132
+
## Ports and Port forwarding
100
133
101
-
Your workspace is now accessible via `ssh coder.<workspace_name>` (e.g.,
102
-
`ssh coder.myEnv` if your workspace is named `myEnv`).
134
+
You can manage listening ports on your workspace page through with the listening ports window in the dashboard. These ports are often used to run internal services or preview environments.
103
135
136
+
You can also [share ports](./port-forwarding.md#sharing-ports) with other users, or [port-forward](./port-forwarding.md#the-coder-port-forward-command) through the CLI with `coder port forward`. Read more in the [docs on workspace ports](./port-forwarding.md).
0 commit comments