zed/crates/collab
Antonio Scandurra 4a61e2dfa4 Save server operations that were in the middle of being applied
Previously, if the test panicked before it had a chance to fully
apply an operation, it would end up not being saved in the plan.
With this commit we will mark the operation as applied before we
start processing it, and mark it as not applied if, once we're done,
we've found out that it couldn't be applied. This is consistent with
what we do for client operations.
2023-04-06 16:02:16 +02:00
..
k8s Encode db-max-connections env var as a string in k8s manifest 2023-03-10 17:19:16 -08:00
migrations Begin tracking follow states on collab server 2023-02-22 11:21:23 -05:00
migrations.sqlite Add followers table to sqlite scheme for tests 2023-02-22 11:22:37 -05:00
src Save server operations that were in the middle of being applied 2023-04-06 16:02:16 +02:00
.env.toml Increase the amount of max connections to the database 2023-03-10 10:10:59 +01:00
basic.conf
Cargo.toml Use the same serde version across the entire workspace 2023-03-28 09:42:00 -07:00
README.md

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.