zed/crates/collab
Antonio Scandurra 9adbab5d99 Fix opening a buffer after leaving and joining the same project
This bug existed prior to #1700 and was caused by not clearing the
buffers that were already shared with a peer that left and opened
a project using the same connection. When such peer would re-join
the project and open a buffer that it had opened previously, the
host assumed the peer had already seen that buffer and wouldn't bother
sending it again.
2022-10-12 10:31:06 +02:00
..
k8s Move prometheus annotations from deployment to pod spec 2022-06-10 14:32:36 -07:00
migrations add proto stuff 2022-10-02 18:01:37 -07:00
src Fix opening a buffer after leaving and joining the same project 2022-10-12 10:31:06 +02:00
.env.toml Added env toml so readme db instructions are correct 2022-08-10 15:07:02 -07:00
basic.conf Rename zed-server to collab 2022-04-09 08:30:42 -06:00
Cargo.toml Finished refactoring out fs and rope 2022-10-11 15:25:54 -07: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.