mirror of
https://github.com/zed-industries/zed.git
synced 2024-09-20 02:47:34 +03:00
cb4f868815
This PR provides some of the plumbing needed for a "remote" zed instance. The way this will work is: * From zed on your laptop you'll be able to manage a set of dev servers, each of which is identified by a token. * You'll run `zed --dev-server-token XXXX` to boot a remotable dev server. * From the zed on your laptop you'll be able to open directories and work on the projects on the remote server (exactly like collaboration works today). For now all this PR does is provide the ability for a zed instance to sign in using a "dev server token". The next steps will be: * Adding support to the collaboration protocol to instruct a dev server to "open" a directory and share it into a channel. * Adding UI to manage these servers and tokens (manually for now) Related #5347 Release Notes: - N/A --------- Co-authored-by: Nathan <nathan@zed.dev>
8 lines
255 B
SQL
8 lines
255 B
SQL
CREATE TABLE dev_servers (
|
|
id INT PRIMARY KEY GENERATED ALWAYS AS IDENTITY,
|
|
channel_id INT NOT NULL REFERENCES channels(id),
|
|
name TEXT NOT NULL,
|
|
hashed_token TEXT NOT NULL
|
|
);
|
|
CREATE INDEX idx_dev_servers_on_channel_id ON dev_servers (channel_id);
|