mirror of
https://github.com/zed-industries/zed.git
synced 2024-12-27 02:48:34 +00:00
78 lines
3.1 KiB
Markdown
78 lines
3.1 KiB
Markdown
# Zed
|
|
|
|
[](https://github.com/zed-industries/zed/actions/workflows/ci.yml)
|
|
|
|
Welcome to Zed, a lightning-fast, collaborative code editor that makes your dreams come true.
|
|
|
|
## Development tips
|
|
|
|
### Dependencies
|
|
|
|
* Install [Postgres.app](https://postgresapp.com) and start it.
|
|
* Install the `LiveKit` server and the `foreman` process supervisor:
|
|
|
|
```
|
|
brew install livekit
|
|
brew install foreman
|
|
```
|
|
|
|
* Ensure the Zed.dev website is checked out in a sibling directory:
|
|
|
|
```
|
|
cd ..
|
|
git clone https://github.com/zed-industries/zed.dev
|
|
```
|
|
|
|
* Initialize submodules
|
|
|
|
```
|
|
git submodule update --init --recursive
|
|
```
|
|
|
|
* Set up a local `zed` database and seed it with some initial users:
|
|
|
|
Create a personal GitHub token to run `script/bootstrap` once successfully: the token needs to have an access to private repositories for the script to work (`repo` OAuth scope).
|
|
Then delete that token.
|
|
|
|
```
|
|
GITHUB_TOKEN=<$token> script/bootstrap
|
|
```
|
|
|
|
### Testing against locally-running servers
|
|
|
|
Start the web and collab servers:
|
|
|
|
```
|
|
foreman start
|
|
```
|
|
|
|
If you want to run Zed pointed at the local servers, you can run:
|
|
|
|
```
|
|
script/zed-with-local-servers
|
|
# or...
|
|
script/zed-with-local-servers --release
|
|
```
|
|
|
|
### Dump element JSON
|
|
|
|
If you trigger `cmd-alt-i`, Zed will copy a JSON representation of the current window contents to the clipboard. You can paste this in a tool like [DJSON](https://chrome.google.com/webstore/detail/djson-json-viewer-formatt/chaeijjekipecdajnijdldjjipaegdjc?hl=en) to navigate the state of on-screen elements in a structured way.
|
|
|
|
### Licensing
|
|
|
|
We use [`cargo-about`](https://github.com/EmbarkStudios/cargo-about) to automatically comply with open source licenses. If CI is failing, check the following:
|
|
|
|
- Is it showing a `no license specified` error for a crate you've created? If so, add `publish = false` under `[package]` in your crate's Cargo.toml.
|
|
- Is the error `failed to satisfy license requirements` for a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to the `accepted` array in `script/licenses/zed-licenses.toml`.
|
|
- Is `cargo-about` unable to find the license for a dependency? If so, add a clarification field at the end of `script/licenses/zed-licenses.toml`, as specified in the [cargo-about book](https://embarkstudios.github.io/cargo-about/cli/generate/config.html#crate-configuration).
|
|
|
|
|
|
### Wasm Plugins
|
|
|
|
Zed has a Wasm-based plugin runtime which it currently uses to embed plugins. To compile Zed, you'll need to have the `wasm32-wasi` toolchain installed on your system. To install this toolchain, run:
|
|
|
|
```bash
|
|
rustup target add wasm32-wasi
|
|
```
|
|
|
|
Plugins can be found in the `plugins` folder in the root. For more information about how plugins work, check the [Plugin Guide](./crates/plugin_runtime/README.md) in `crates/plugin_runtime/README.md`.
|