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>
38 lines
922 B
Rust
38 lines
922 B
Rust
pub mod access_token;
|
|
pub mod buffer;
|
|
pub mod buffer_operation;
|
|
pub mod buffer_snapshot;
|
|
pub mod channel;
|
|
pub mod channel_buffer_collaborator;
|
|
pub mod channel_chat_participant;
|
|
pub mod channel_member;
|
|
pub mod channel_message;
|
|
pub mod channel_message_mention;
|
|
pub mod contact;
|
|
pub mod contributor;
|
|
pub mod dev_server;
|
|
pub mod extension;
|
|
pub mod extension_version;
|
|
pub mod feature_flag;
|
|
pub mod follower;
|
|
pub mod hosted_project;
|
|
pub mod language_server;
|
|
pub mod notification;
|
|
pub mod notification_kind;
|
|
pub mod observed_buffer_edits;
|
|
pub mod observed_channel_messages;
|
|
pub mod project;
|
|
pub mod project_collaborator;
|
|
pub mod rate_buckets;
|
|
pub mod room;
|
|
pub mod room_participant;
|
|
pub mod server;
|
|
pub mod signup;
|
|
pub mod user;
|
|
pub mod user_feature;
|
|
pub mod worktree;
|
|
pub mod worktree_diagnostic_summary;
|
|
pub mod worktree_entry;
|
|
pub mod worktree_repository;
|
|
pub mod worktree_repository_statuses;
|
|
pub mod worktree_settings_file;
|