| Filename | Latest commit message | Latest commit date |
|---|---|---|
ebbc7743e7
Move the whole workspace to Rust 1.97 (from 1.96) and bump ~120 dependencies to their latest major versions. The full 230-crate workspace compiles, joule_core's 182 tests pass, the release daemon builds, and LFM2 still loads + runs. API adaptations for the major bumps: - rand 0.10: rand_core renamed RngCore->Rng and moved the sugar (random_range, from_os_rng) onto RngExt / removed it — updated call sites + imports. - yawc 0.3: FrameView->Frame with accessor methods; client socket is TcpWebSocket. - sqlx 0.9 / heed 0.22 / axum 0.8: renamed/removed cargo features. - core-video 0.6: create_texture_from_image takes &CVImageBuffer; convert via TCVImageBuffer::as_image_buffer. - prost: Message no longer implies Debug — added the bound. - cargo_toml 1.0: lints is now Inheritable<LintGroups> (Inherited == workspace). - ed25519-dalek, core-text, core-graphics, cpal: pinned to the versions the git-forked deps (open-standands receipts, zed-font-kit, rodio) are built against — a split breaks shared SigningKey/CTFont/CGFont/Device types. Deliberate holds (their own migration, not a blind sweep): - livekit/libwebrtc/webrtc-sys/coreaudio-rs: the real-time A/V stack, pinned to Zed's livekit-rust-sdks fork; latest breaks livekit_client deeply. - wasmtime 36 + wit-bindgen 0.41: the extension component-model ABI, tied to the pinned zed:extension WIT worlds. - brush-parser 0.3: 0.4 reshapes the AST on the command-safety allow-gate path. - runtimelib/nbformat/jupyter-protocol 1.x: the REPL Jupyter stack moves majors together. Also: unlisted Zed's hosted-collab SERVER (crates/collab) from the workspace — a leaf binary nothing depends on, whose pinned sea-orm/sqlx chain blocked the upgrade; source stays on disk. All open-standards git deps repointed to the forge URL and bumped to c4b536cf (320fa1e + score_binary). Co-Authored-By: Claude Opus 4.8 <[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.