Allow ssh connection for setting up zed

[ConradIrwin]

Co-Authored-By: Mikayla [email protected]

Release Notes:

• Magic ssh login feature for remote development

[JesseFarebro]

Hi! Just an observer who's looking forward to remote dev functionality. On multi-tenant machines, e.g., HPC clusters it would be ideal if Zed either a) finds an open port instead of relying on 8080 or the RPC environment variable or b) can optionally use unix sockets which can be forwarded over SSH and is more secure as other users on the cluster wouldn't be able to see or interact with the RPC endpoint.

Thanks for the great work on this 🎉

[ConradIrwin]

:+1: Definitely! This branch is actually only taken (right now at least) while developing zed. In the deployed version the two communicate via https://collab.zed.dev. (In a future iteration that might change, and we should definitely make the port dynamic then).

[JesseFarebro]

👍 Definitely! This branch is actually only taken (right now at least) while developing zed. In the deployed version the two communicate via https://collab.zed.dev. (In a future iteration that might change, and we should definitely make the port dynamic then).

Ahh, I see. I believe I read this in the notes on the remoting channel but to add another +1: it might be nice to support remote development when the remote machine doesn't have an internet connection. VSCode handles this nicely and this does show up quite frequently with HPC clusters.

[ConradIrwin]

@JesseFarebro definitely! I didn't want to give people a false sense of privacy though - so although we could technically proxy requests to https://collab.zed.dev over SSH, I'd rather wait until we're further along in supporting a hub-less collaboration model.