-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JetBrains Fleet: Add a 1-click button for launching Fleet #246
Comments
Is it possible to have a Fleet extension? |
@kylecarbs not yet. But it's on their long-term roadmap. No developers docs ATM. |
Yeah without an extension the best we can do is document that |
This is insane, but I'm pretty sure Chrome handles In some magically insane world, we could add a small sniffer to the initial HTTPS packet for the SSH prefix (e.g. |
Woaaaah that is actually dope. |
nice, what awesome about fleet is that it's free, for now. |
Maybe in preparation the fleet icon can be added to the coder server ;) Also you do need have your ssh config updated ahead of time. |
For sure you can access the server via chrome: |
It should be |
i see that fleet 1.37 now out and this url schema works well :) |
@matifali i added the fleet icon to coder so long coder/coder#14021 |
And there is no way to know that the coder cli was installed locally or that |
Sadly yes for now. It might change in future when Fleet support extensions or We find another way probably through Coder chrome extension. |
The same problem exists for people using JetBrains IDE (you need to pre-install Jetbrain Gateway). |
May be we can use https://www.jetbrains.com/help/fleet/install-on-a-remote-machine.html |
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:
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
andport
can also be specified alongside thehostname
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 specifyingpwd
will open an empty workspace on the host.Examples:
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.
The text was updated successfully, but these errors were encountered: