Change on remote setup and one more SSH command as example (#12591)

Release Notes:
- N/A
This commit is contained in:
Francisco Rivas 2024-06-03 10:34:09 +02:00 committed by GitHub
parent b218d8778d
commit d0142b820f
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -16,7 +16,7 @@ Currently the two instances connect via Zed's servers, but we intend to build pe
1. Download and install the latest [Zed Preview](https://zed.dev/releases/preview). 1. Download and install the latest [Zed Preview](https://zed.dev/releases/preview).
1. Open the remote projects dialogue with `cmd-shift-p remote`. 1. Open the remote projects dialogue with `cmd-shift-p remote`.
2. Click "Add Server". 2. Click "New Server".
3. Choose whether to setup via SSH, or to follow the manual setup. 3. Choose whether to setup via SSH, or to follow the manual setup.
> **Note:** With both options your laptop and the remote machine will communicate > **Note:** With both options your laptop and the remote machine will communicate
via https://collab.zed.dev/, so you will need outbound internet access on the remote machine. via https://collab.zed.dev/, so you will need outbound internet access on the remote machine.
@ -47,6 +47,7 @@ can specify:
- `gh cs ssh -c example-codespace` to connect to a GitHub codespace - `gh cs ssh -c example-codespace` to connect to a GitHub codespace
- `doctl compute ssh example-droplet` to connect to a DigitalOcean Droplet - `doctl compute ssh example-droplet` to connect to a DigitalOcean Droplet
- `gcloud compute ssh` for a Google Cloud instance - `gcloud compute ssh` for a Google Cloud instance
- `ssh -i path_to_key_file user@host` to connect to a host using a key file or certificate
### zed --dev-server-token isn't connecting ### zed --dev-server-token isn't connecting