Yehowshua/ZIm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
ZIm/crates/collab
History
Max Brunsfeld 647b08b101
Update local development workflow to not involve zed.dev (#4103) 
When testing Zed locally, it's rarely necessary to log in the real with,
via Zed.dev and GitHub. We usually use `zed-local`. Since zed.dev is not
going to be open source (at least right away), this PR removes it from
our local development workflow.

* Remove zed.dev from the Procfile
* Change the `seed` script to not create an admin user for your
signed-in github user
* Instead have both `zed-local` and the `seed` script read from an
`.admins.json` file, which the user can create in order to customize who
they sign in as when running `zed-local`.
* Update all of the docs for building and developing zed.
2024-01-17 15:07:20 -08:00
..
k8s Deploy tweaks 2024-01-05 13:24:29 -07:00
migrations Switch to non-destructive migration 2024-01-11 10:33:33 -08:00
migrations.sqlite enviroment -> environment 2024-01-10 22:57:58 -08:00
src Update local development workflow to not involve zed.dev (#4103) 2024-01-17 15:07:20 -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 Increase the amount of max connections to the database 2023-03-10 10:10:59 +01:00
admin_api.conf Run postgrest as part of foreman 2023-09-13 12:32:15 -07:00
basic.conf Rename zed-server to collab 2022-04-09 08:30:42 -06:00
Cargo.toml collab 0.36.1 2024-01-11 11:00:42 -08:00
README.md Remove more files supporting the old web front-end 2022-04-21 09:06:34 -06: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.