mirror of https://github.com/zed-industries/zed.git synced 2024-12-27 02:48:34 +00:00

History

Antonio Scandurra a41eb5a663 Ensure server always responds when receiving a request		2022-02-13 10:21:01 +01:00
..
k8s	Add placeholder environment variables to our deploy	2022-01-12 16:33:41 -07:00
migrations
src	Ensure server always responds when receiving a request	2022-02-13 10:21:01 +01:00
static
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	Try another hacky approach for tearing down DBs after all tests	2022-02-07 15:23:35 -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.