zed/crates/collab
Antonio Scandurra 6212f2fe30 Wait for remote worktree to catch up with host before mutating entries
This ensures that entries don't randomly re-appear on remote worktrees
due to observing an update too late. In fact, it ensures that the remote
worktree has the same starting state of the host before preemptively applying
the fs operation locally.
2022-05-05 13:47:53 +02:00
..
k8s Start moving from logging to tracing on collab server 2022-04-28 09:45:59 -06:00
migrations Drop signups table 2022-04-21 10:59:13 -06:00
src Wait for remote worktree to catch up with host before mutating entries 2022-05-05 13:47:53 +02:00
.env.template.toml Remove remaining bits of web front-end 2022-04-21 09:30:08 -06:00
basic.conf Rename zed-server to collab 2022-04-09 08:30:42 -06:00
Cargo.toml Revert "WIP" 2022-04-29 16:45:29 +02:00
Procfile Rename zed-server to collab 2022-04-09 08:30:42 -06:00
README.md Remove more files supporting the old web front-end 2022-04-21 09:06:34 -06:00

Zed Server

This crate is what we run at https://collab.zed.dev.

It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://zed.dev, which is a separate repo running on Vercel.