zed/crates/collab
Max Brunsfeld 6b320b9efe
Fix cleanup of LSP request status messages (#10336)
This fixes a bug in https://github.com/zed-industries/zed/pull/9818,
where the status was not removed if the request failed. It also adds
replication of these new status messages to guests when collaborating.

Release Notes:

- Fixed an issue where the status of failed LSP actions was left in the
status bar

---------

Co-authored-by: Marshall <marshall@zed.dev>
Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>
2024-04-09 17:34:51 -04:00
..
k8s Remove datadog (#10133) 2024-04-03 11:35:23 -06:00
migrations Add telemetry events for loading extensions (#9793) 2024-03-25 17:30:48 -04:00
migrations.sqlite Add telemetry events for loading extensions (#9793) 2024-03-25 17:30:48 -04:00
src Fix cleanup of LSP request status messages (#10336) 2024-04-09 17:34:51 -04:00
.env.toml Make it (a tiny bit) easier to run your own collab (#9557) 2024-03-20 21:00:02 -06:00
admin_api.conf Run postgrest as part of foreman 2023-09-13 12:32:15 -07:00
Cargo.toml Enable Claude 3 models to be used via the Zed server if "language-models" feature flag is enabled for user (#10015) 2024-03-31 15:57:57 -06:00
LICENSE-AGPL chore: Add crate licenses. (#4158) 2024-01-23 16:56:22 +01:00
README.md remoting (#9680) 2024-03-22 08:44:56 -06:00
seed.default.json Make it (a tiny bit) easier to run your own collab (#9557) 2024-03-20 21:00:02 -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.

Local Development

Detailed instructions on getting started are here.

Deployment

We run two instances of collab:

Both of these run on the Kubernetes cluster hosted in Digital Ocean.

Deployment is triggered by pushing to the collab-staging (or collab-production) tag in Github. The best way to do this is:

  • ./script/deploy-collab staging
  • ./script/deploy-collab production

You can tell what is currently deployed with ./script/what-is-deployed.

Database Migrations

To create a new migration:

./script/create-migration <name>

Migrations are run automatically on service start, so run foreman start again. The service will crash if the migrations fail.

When you create a new migration, you also need to update the SQLite schema that is used for testing.