Files

T

Max BrunsfeldandConrad 5b35dedc5f Add nightly environment for collab

Also, move postgrest service + deployment into a separate manifest
file, which is deployed via a separate script, `deploy-postgrest`.
This way, we don't have unused postgrest instances in preview and
nightly, since those use the prod database.

Co-authored-by: Conrad <conrad@zed.dev>

2024-01-02 14:29:21 -08:00

k8s

Add nightly environment for collab

2024-01-02 14:29:21 -08:00

migrations

Get collab2 green

2023-11-03 18:01:06 -07:00

migrations.sqlite

Get collab2 green

2023-11-03 18:01:06 -07:00

src

Rename build_view to new_view and build_model to new_model (#3823 )

2024-01-02 08:11:53 -07:00

.env.toml

Get collab2 green

2023-11-03 18:01:06 -07:00

admin_api.conf

Get collab2 green

2023-11-03 18:01:06 -07:00

basic.conf

Get collab2 green

2023-11-03 18:01:06 -07:00

Cargo.toml

Fix propagation of active item to followers

2023-12-06 12:18:48 -08:00

README.md

Get collab2 green

2023-11-03 18:01:06 -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.