zed/crates/collab
Max Brunsfeld ab1bea515c Store the impersonator id on access tokens created via ZED_IMPERSONATE
* Use the impersonator id to prevent these tokens from counting
  against the impersonated user when limiting the users' total
  of access tokens.
* When connecting using an access token with an impersonator
  add the impersonator as a field to the tracing span that wraps
  the task for that connection.
* Disallow impersonating users via the admin API token in production,
  because when using the admin API token, we aren't able to identify
  the impersonator.

Co-authored-by: Marshall <marshall@zed.dev>
2024-01-17 18:06:16 -08:00
..
k8s Deploy tweaks 2024-01-05 13:24:29 -07:00
migrations Store the impersonator id on access tokens created via ZED_IMPERSONATE 2024-01-17 18:06:16 -08:00
migrations.sqlite Store the impersonator id on access tokens created via ZED_IMPERSONATE 2024-01-17 18:06:16 -08:00
src Store the impersonator id on access tokens created via ZED_IMPERSONATE 2024-01-17 18:06:16 -08:00
.admins.default.json Rework db-seeding, so that it doesn't depend on a github auth token 2024-01-17 13:28:58 -08: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.36.1 2024-01-11 11:00:42 -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.