Marshall BowersandMax
50fc54c321
This PR extends the extension API with some additional features to support auto-updating extensions: - The `GET /extensions` endpoint now accepts an optional `ids` parameter that can be used to filter the results down to just the extensions with the specified IDs. - This should be a comma-delimited list of extension IDs (e.g., `wgsl,gleam,tokyo-night`). - A new `GET /extensions/:extension_id` endpoint that returns all of the extension versions for a particular extension. Extracted from #9890, as these changes can be landed and deployed independently. Release Notes: - N/A Co-authored-by: Max <max@zed.dev>
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:
- Staging (https://staging-collab.zed.dev)
- Production (https://collab.zed.dev)
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.