Description
As per this Fleet issue, it will soon support launching remote environments via a URI scheme.
With Fleet 1.36 (the version after the upcoming version 1.35), Fleet URI handler will support connecting to SSH directly using URIs of this format:
fleet://fleet.ssh/<hostname>?<query_params>
with possible params being
username
port
pwd
(the working directory to open)forceNewHost
(possible values aretrue
andfalse
, default isfalse
- Setting to true will let Fleet ignore previous known hosts and always create a new connection)
username
and port
can also be specified alongside the hostname
in common SSH URI syntax, i.e., <username>@<hostname>:<port>
. To avoid ambiguities, pwd
can only be specified explicitly.
Only the hostname
is required. If some parameters are not specified, Fleet will try to use the closest known match in previous connections or fall back to default values. .ssh/config
is considered as usual. Not specifying pwd
will open an empty workspace on the host.
Examples:
fleet://fleet.ssh/example.org?username=foo&pwd=/home/foo/my_test_project
fleet://fleet.ssh/[email protected]?pwd=/home/foo/my_test_project
The current process to connect to a Coder workspace is documented here: https://coder.com/docs/ides/fleet
@kylecarbs @code-asher, what are your thoughts on how we can dynamically populate the URI? We have our plugins for VSCode Desktop and JetBrains gateway, which populates the .ssh/config
.
Update: Fleet 1.36, which supports the SSH connection URI, has been released.