mirrors/zed
1
0
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2025-01-09 10:56:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 9
zed/crates/collab/README.md

38 lines
1.2 KiB
Markdown
Raw Normal View History

Include contents of the zed-server repo We're going full monorepo. Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-07-12 20:14:39 +00:00
# Zed Server
Remove more files supporting the old web front-end
2022-04-21 15:06:34 +00:00
This crate is what we run at https://collab.zed.dev.
Include contents of the zed-server repo We're going full monorepo. Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-07-12 20:14:39 +00:00
Remove more files supporting the old web front-end
2022-04-21 15:06:34 +00:00
It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://zed.dev, which is a separate repo running on Vercel.
Deploy collab like nightly (#7174) After this change we'll be able to push a tag to github to deploy to collab. The advantages of this are that there's no longer a separate step to first build the image, and then deploy it. In the future I'd like to make this happen more automatically (maybe as part of bump nightly). Release Notes: - N/A
2024-02-01 18:54:49 +00:00
# Local Development
Make it (a tiny bit) easier to run your own collab (#9557) * Allow creating channels when seeding * Allow configuring a custom `SEED_PATH` * Seed the database when creating/migrating it so you don't need a separate step for this. Release Notes: - N/A
2024-03-21 03:00:02 +00:00
Detailed instructions on getting started are [here](https://zed.dev/docs/local-collaboration).
Deploy collab like nightly (#7174) After this change we'll be able to push a tag to github to deploy to collab. The advantages of this are that there's no longer a separate step to first build the image, and then deploy it. In the future I'd like to make this happen more automatically (maybe as part of bump nightly). Release Notes: - N/A
2024-02-01 18:54:49 +00:00
# Deployment
We run two instances of collab:
Make it (a tiny bit) easier to run your own collab (#9557) * Allow creating channels when seeding * Allow configuring a custom `SEED_PATH` * Seed the database when creating/migrating it so you don't need a separate step for this. Release Notes: - N/A
2024-03-21 03:00:02 +00:00
- Staging (https://staging-collab.zed.dev)
- Production (https://collab.zed.dev)
Deploy collab like nightly (#7174) After this change we'll be able to push a tag to github to deploy to collab. The advantages of this are that there's no longer a separate step to first build the image, and then deploy it. In the future I'd like to make this happen more automatically (maybe as part of bump nightly). Release Notes: - N/A
2024-02-01 18:54:49 +00:00
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:
Make it (a tiny bit) easier to run your own collab (#9557) * Allow creating channels when seeding * Allow configuring a custom `SEED_PATH` * Seed the database when creating/migrating it so you don't need a separate step for this. Release Notes: - N/A
2024-03-21 03:00:02 +00:00
- `./script/deploy-collab staging`
- `./script/deploy-collab production`
Deploy collab like nightly (#7174) After this change we'll be able to push a tag to github to deploy to collab. The advantages of this are that there's no longer a separate step to first build the image, and then deploy it. In the future I'd like to make this happen more automatically (maybe as part of bump nightly). Release Notes: - N/A
2024-02-01 18:54:49 +00:00
You can tell what is currently deployed with `./script/what-is-deployed`.
# Database Migrations
To create a new migration:
```
remoting (#9680) This PR provides some of the plumbing needed for a "remote" zed instance. The way this will work is: * From zed on your laptop you'll be able to manage a set of dev servers, each of which is identified by a token. * You'll run `zed --dev-server-token XXXX` to boot a remotable dev server. * From the zed on your laptop you'll be able to open directories and work on the projects on the remote server (exactly like collaboration works today). For now all this PR does is provide the ability for a zed instance to sign in using a "dev server token". The next steps will be: * Adding support to the collaboration protocol to instruct a dev server to "open" a directory and share it into a channel. * Adding UI to manage these servers and tokens (manually for now) Related #5347 Release Notes: - N/A --------- Co-authored-by: Nathan <nathan@zed.dev>
2024-03-22 14:44:56 +00:00
./script/create-migration <name>
Deploy collab like nightly (#7174) After this change we'll be able to push a tag to github to deploy to collab. The advantages of this are that there's no longer a separate step to first build the image, and then deploy it. In the future I'd like to make this happen more automatically (maybe as part of bump nightly). Release Notes: - N/A
2024-02-01 18:54:49 +00:00
```
Migrations are run automatically on service start, so run `foreman start` again. The service will crash if the migrations fail.
When you create a new migration, you also need to update the [SQLite schema](./migrations.sqlite/20221109000000_test_schema.sql) that is used for testing.
Reference in a new issue Copy permalink