zed/crates/collab
Nathan Sobo fb246ac343 Log JSON in Kubernetes
If you set LOG_JSON=true, we'll output JSON from the tracing subscriber instead of pretty-printing trace output.

Co-Authored-By: Antonio Scandurra <me@as-cii.com>
2022-05-17 11:05:22 -06:00
..
k8s Log JSON in Kubernetes 2022-05-17 11:05:22 -06:00
migrations Start work on RPC endpoints for dealing with contact requests 2022-05-06 15:44:47 -07:00
src Log JSON in Kubernetes 2022-05-17 11:05:22 -06:00
.env.template.toml Remove remaining bits of web front-end 2022-04-21 09:30:08 -06:00
basic.conf Rename zed-server to collab 2022-04-09 08:30:42 -06:00
Cargo.toml Log JSON in Kubernetes 2022-05-17 11:05:22 -06:00
Procfile Rename zed-server to collab 2022-04-09 08:30:42 -06:00
README.md Remove more files supporting the old web front-end 2022-04-21 09:06:34 -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.