mirrors/zed
1
0
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2024-12-28 11:29:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10
zed/crates/server
History
Antonio Scandurra 31dfd01fda Make add_local_worktree private and use find_or_create_local_worktree 
The former always adds a worktree, even if we have one already in the
project and that could be misused. The public API should always search
for a local worktree containing the requested path first so that the
project can uphold invariants about which worktrees it has.
2022-01-22 11:23:00 +01:00
..
k8s Add placeholder environment variables to our deploy 2022-01-12 16:33:41 -07:00
migrations
src Make add_local_worktree private and use find_or_create_local_worktree 2022-01-22 11:23:00 +01:00
static Fix paths to server crate in scripts and gitignore 2021-11-03 19:22:00 -07:00
templates Add job post to Zed.dev 2021-12-23 23:22:57 -05:00
.env.template.toml
.env.toml Add the fetching of user JSON by github login with a token header 2021-12-19 09:43:13 -07:00
basic.conf
Cargo.toml Allow the zed app to connect to both the old and new rpc endpoints 2022-01-03 15:29:26 -08:00
favicon.ico
Procfile
README.md
styles.css

README.md

Zed Server

This crate is what we run at https://zed.dev.

It contains our web presence as well as the backend logic for collaboration, to which we connect from the Zed client via a websocket.

Templates

We use handlebars templates that are interpreted at runtime. When running in debug mode, you can change templates and see the latest content without restarting the server. This is enabled by the rust-embed crate, which we use to access the contents of the /templates folder at runtime. In debug mode it reads contents from the file system, but in release the templates will be embedded in the server binary.

Static assets

We also use rust-embed to access the contents of the /static folder via the /static/* route. The app will pick up changes to the contents of this folder when running in debug mode.

CSS

This site uses Tailwind CSS, which means our stylesheets don't need to change very frequently. We check static/styles.css into the repository, but it's actually compiled from /styles.css via script/build-css. This script runs the Tailwind compilation flow to regenerate static/styles.css via PostCSS.