mirror of
https://github.com/zed-industries/zed.git
synced 2025-02-09 12:01:58 +00:00
SSH Remoting: Document manual binary management (#19862)
Release Notes: - N/A
This commit is contained in:
parent
93b20008e0
commit
a3f0bb4547
1 changed files with 3 additions and 1 deletions
|
@ -113,7 +113,9 @@ Any prompts that SSH needs will be shown in the UI, so you can verify host keys,
|
|||
|
||||
Once the master connection is established, Zed will check to see if the remote server binary is present in `~/.zed_server` on the remote, and that its version matches the current version of Zed that you're using.
|
||||
|
||||
If it is not there or the version mismatches, Zed will try to download the latest version. By default, it will download from `https://zed.dev` directly, but if you set: `{"remote_server": {"download":false}}` in your local settings, it will download the binary to your local machine and then upload it to the remote server.
|
||||
If it is not there or the version mismatches, Zed will try to download the latest version. By default, it will download from `https://zed.dev` directly, but if you set: `{"upload_binary_over_ssh":true}` in your settings for that server, it will download the binary to your local machine and then upload it to the remote server.
|
||||
|
||||
If you'd like to maintain the server binary yourself you can. You can either download our prebuilt versions from [Github](https://github.com/zed-industries/zed/releases), or [build your own](https://zed.dev/docs/development) with `cargo build -p remote_server --release`. If you do this, you must upload it to `~/.zed_server/zed-remote-server-{RELEASE_CHANNEL}-{OS}-{ARCH}` on the server, for example `.zed-server/zed-remote-server-preview-linux-x86_64`. The version must exactly match the version of Zed itself you are using.
|
||||
|
||||
## Maintaining the SSH connection
|
||||
|
||||
|
|
Loading…
Reference in a new issue