zed/crates/collab
Antonio Scandurra 4b1dcf2d55 Always use strings to represent paths over the wire
Previously, the protocol used a mix of strings and bytes without any consistency.

When we go to multiple platforms, we won't be able to mix encodings of paths anyway.
We don't know this is the right approach, but it at least makes things consistent
and easy to read in the database, on the wire, etc. Really, we should be using entry
ids etc to refer to entries on the wire anyway, but there's a chance this is the
wrong decision.

Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2022-11-15 16:46:17 +01:00
..
k8s Update DO SSL certificate id in kube manifest 2022-10-26 16:19:19 -07:00
migrations Move Store::join_project to Db::join_project 2022-11-15 16:37:51 +01:00
migrations.sqlite Move Store::join_project to Db::join_project 2022-11-15 16:37:51 +01:00
src Always use strings to represent paths over the wire 2022-11-15 16:46:17 +01:00
.env.toml Merge branch 'main' into screen-sharing 2022-10-21 14:29:45 +02:00
basic.conf Rename zed-server to collab 2022-04-09 08:30:42 -06:00
Cargo.toml Use upstream sqlx git repository 2022-11-10 15:13:32 -08: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.