zed/crates/collab
Max Brunsfeld 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
..
migrations Remove logic for multiple channel parents 2023-10-24 17:29:23 +02:00
migrations.sqlite Remove logic for multiple channel parents 2023-10-24 17:29:23 +02:00
src Add backtrace hash to collab server panic api 2023-12-18 11:12:23 -05:00
.env.toml
admin_api.conf Run postgrest as part of foreman 2023-09-13 12:32:15 -07:00
basic.conf
Cargo.toml collab 0.32.0 2023-12-20 13:15:44 -05:00
k8s Add nightly environment for collab 2024-01-02 14:29:21 -08: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.