Files

T

Max Brunsfeld 877d67b97d Provide an admin REST API for use by zed.dev (#2962 )

We're using [PostgREST](https://hub.docker.com/r/postgrest/postgrest)

Todo:
* [x] Add instructions for installing postgrest to local development
docs
* [x] Deploy to staging
* [x] Deploy to production
* [x] Add DNS record for `admin-staging.zed.dev` pointing to the staging
db
* [x] Add a DNS record for `admin.zed.dev` pointing to the production db

2023-09-14 13:48:54 -07:00

k8s

Use PostgREST instead of pgAdmin

2023-09-13 11:47:20 -07:00

migrations

Update database and RPC to provide configured feature flags

2023-08-25 14:34:32 -07:00

migrations.sqlite

Update database and RPC to provide configured feature flags

2023-08-25 14:34:32 -07:00

src

Remove dead code for old admin pages

2023-09-13 15:02:59 -07: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.21.0

2023-09-13 13:34:08 -04: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.