| Filename | Latest commit message | Latest commit date |
|---|---|---|
4e1eb7ab71
Continues the earlier pass. Each sweep can only check crates whose dependencies compiled, so every round reached deeper and uncovered another layer: 16, 35, 7, 12, 15, 69, 31, 1, then a long tail. The spikes are large crates unblocking — `project` in one round, the `editor` tree in another — not new breakage. Nearly all of it applied from rustc's own machine-applicable spans. Judgement was needed in a few places: prost's `from_i32` becomes `try_from(..).ok()` at 24 sites, written that way because every caller wanted an `Option` and `.ok()` keeps the semantics identical; a paren-matching rewrite rather than a regex, since the argument is often itself a call. `criterion::black_box` moved to `std::hint`, `rand`'s `choose_multiple` is `sample`, and `time::format_description::parse` is `parse_borrowed::<2>`. Two are deliberately marked rather than changed. `SettingsInputField`'s four builder methods really are unused — the other `with_id` hits in the tree are `window.with_id` — so they carry `#[allow(dead_code)]` and a note rather than being deleted out of a fork. `open_ai`'s large `Err` variant keeps its scoped allow for the reason given there. One lint was ours: the panel had a manual checked division, now `checked_div`. Co-Authored-By: Claude Opus 5 <[email protected]> |
||
| .. | ||
| k8s | ||
| migrations | ||
| migrations.sqlite | ||
| seed | ||
| src | ||
| tests/integration | ||
| .env.toml | ||
| Cargo.toml | ||
| LICENSE-GPL | ||
| README.md | ||
| seed.default.json | ||
Joule Server
This crate is what we run at https://collab.transaction.science.
It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://transaction.science, which is a separate repo running on Vercel.
Local Development
Database setup
Before you can run the collab server locally, you'll need to set up a zed Postgres database. Follow the steps sequentially:
- Ensure you have postgres installed. If not, install with
brew install postgresql@15. - Follow the steps on Brew's formula and verify your
$PATHcontains/opt/homebrew/opt/postgresql@15/bin. - If you hadn't done it before, create the
postgresuser withcreateuser -s postgres. - You are now ready to run the
bootstrapscript:
script/bootstrap
This script will set up the zed Postgres database, and populate it with some users. It requires internet access, because it fetches some users from the GitHub API.
The script will create several admin users, who you'll sign in as by default when developing locally. The GitHub logins for the default users are specified in the seed.default.json file.
To use a different set of admin users, create crates/collab/seed.json.
{
"admins": ["yourgithubhere"],
"channels": ["zed"]
}
Testing collaborative features locally
In one terminal, run Joule's collaboration server and the livekit dev server:
foreman start
In a second terminal, run two or more instances of Joule.
script/zed-local -2
This script starts one to four instances of Joule, depending on the -2, -3 or -4 flags. Each instance will be connected to the local collab server, signed in as a different user from seed.json or seed.default.json.
Deployment
We run two instances of collab:
- Staging (https://staging-collab.transaction.science)
- Production (https://collab.transaction.science)
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.