windows: Make collab run on Windows (#23117)

I’ve also updated the documentation in
`development\local-collaboration.md` and
`docs\src\development\windows.md`.

Testing collab on my Windows machine:

![屏幕截图 2025-01-14
162021](https://github.com/user-attachments/assets/28b4a36a-e156-4012-981a-5d0a23dcc613)


Release Notes:

- N/A

---------

Co-authored-by: Marshall Bowers <elliott.codes@gmail.com>

docs/src/development/local-collaboration.md

@@ -10,6 +10,8 @@ First, make sure you've installed Zed's backend dependencies for your platform:
 
 Before you can run the `collab` server locally, you'll need to set up a `zed` Postgres database.
 
+### On macOS and Linux
+
 ```sh
 script/bootstrap
 ```
@@ -31,8 +33,16 @@ To use a different set of admin users, you can create your own version of that j
 }
 ```
 
+### On Windows
+
+```powershell
+.\script\bootstrap.ps1
+```
+
 ## Testing collaborative features locally
 
+### On macOS and Linux
+
 Ensure that Postgres is configured and running, then run Zed's collaboration server and the `livekit` dev server:
 
 ```sh
@@ -41,7 +51,7 @@ foreman start
 cargo run -p collab -- serve all
 ```
 
-In a second terminal, run two or more instances of Zed.
+In a new terminal, run two or more instances of Zed.
 
 ```sh
 script/zed-local -2
@@ -49,6 +59,34 @@ script/zed-local -2
 
 This script starts one to four instances of Zed, 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 `.admins.json` or `.admins.default.json`.
 
+### On Windows
+
+Since `foreman` is not available on Windows, you can run the following commands in separate terminals:
+
+```powershell
+cargo run --package=collab -- serve all
+```
+
+If you have added the `livekit-server` binary to your `PATH`, you can run:
+
+```powershell
+livekit-server --dev
+```
+
+Otherwise,
+
+```powershell
+.\path\to\livekit-serve.exe --dev
+```
+
+In a new terminal, run two or more instances of Zed.
+
+```powershell
+node .\script\zed-local -2
+```
+
+Note that this requires `node.exe` to be in your `PATH`.
+
 ## Running a local collab server
 
 If you want to run your own version of the zed collaboration service, you can, but note that this is still under development, and there is no good support for authentication nor extensions.

docs/src/development/windows.md

@@ -12,7 +12,31 @@ Clone down the [Zed repository](https://github.com/zed-industries/zed).
 
 - Install [Visual Studio](https://visualstudio.microsoft.com/downloads/) with the optional components `MSVC v*** - VS YYYY C++ x64/x86 build tools` and `MSVC v*** - VS YYYY C++ x64/x86 Spectre-mitigated libs (latest)` (`v***` is your VS version and `YYYY` is year when your VS was released. Pay attention to the architecture and change it to yours if needed.)
 - Install Windows 11 or 10 SDK depending on your system, but ensure that at least `Windows 10 SDK version 2104 (10.0.20348.0)` is installed on your machine. You can download it from the [Windows SDK Archive](https://developer.microsoft.com/windows/downloads/windows-sdk/)
-- Install [CMake](https://cmake.org/download) (required by [a dependency](https://docs.rs/wasmtime-c-api-impl/latest/wasmtime_c_api/))
+- Install [CMake](https://cmake.org/download) (required by [a dependency](https://docs.rs/wasmtime-c-api-impl/latest/wasmtime_c_api/)). Or you can install it through Visual Studio Installer, then manually add the `bin` directory to your `PATH`, for example: `C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin`.
+
+If you can't compile Zed, make sure that you have at least the following components installed:
+
+```json
+{
+  "version": "1.0",
+  "components": [
+    "Microsoft.VisualStudio.Component.CoreEditor",
+    "Microsoft.VisualStudio.Workload.CoreEditor",
+    "Microsoft.VisualStudio.Component.VC.Tools.x86.x64",
+    "Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions.CMake",
+    "Microsoft.VisualStudio.Component.VC.CMake.Project",
+    "Microsoft.VisualStudio.Component.Windows11SDK.26100",
+    "Microsoft.VisualStudio.Component.VC.Runtimes.x86.x64.Spectre"
+  ],
+  "extensions": []
+}
+```
+
+The list can be obtained as follows:
+
+- Open the Visual Studio Installer
+- Click on `More` in the `Installed` tab
+- Click on `Export configuration`
 
 ## Backend dependencies
 
@@ -21,7 +45,7 @@ Clone down the [Zed repository](https://github.com/zed-industries/zed).
 If you are developing collaborative features of Zed, you'll need to install the dependencies of zed's `collab` server:
 
 - Install [Postgres](https://www.postgresql.org/download/windows/)
-- Install [Livekit](https://github.com/livekit/livekit-cli) and [Foreman](https://theforeman.org/manuals/3.9/quickstart_guide.html)
+- Install [Livekit](https://github.com/livekit/livekit), optionally you can add the `livekit-server` binary to your `PATH`.
 
 Alternatively, if you have [Docker](https://www.docker.com/) installed you can bring up all the `collab` dependencies using Docker Compose:
 
@@ -29,6 +53,26 @@ Alternatively, if you have [Docker](https://www.docker.com/) installed you can b
 docker compose up -d
 ```
 
+### Notes
+
+You should modify the `pg_hba.conf` file in the `data` directory to use `trust` instead of `scram-sha-256` for the `host` method. Otherwise, the connection will fail with the error `password authentication failed`. The `pg_hba.conf` file typically locates at `C:\Program Files\PostgreSQL\17\data\pg_hba.conf`. After the modification, the file should look like this:
+
+```conf
+# IPv4 local connections:
+host    all             all             127.0.0.1/32            trust
+# IPv6 local connections:
+host    all             all             ::1/128                 trust
+```
+
+Also, if you are using a non-latin Windows version, you must modify the`lc_messages` parameter in the `postgresql.conf` file in the `data` directory to `English_United States.1252` (or whatever UTF8-compatible encoding you have). Otherwise, the database will panic. The `postgresql.conf` file should look like this:
+
+```conf
+# lc_messages = 'Chinese (Simplified)_China.936' # locale for system error message strings
+lc_messages = 'English_United States.1252'
+```
+
+After this, you should restart the `postgresql` service. Press the `win` key + `R` to launch the `Run` window. Type the `services.msc` and hit the `OK` button to open the Services Manager. Then, find the `postgresql-x64-XX` service, right-click on it, and select `Restart`.
+
 ## Building from source
 
 Once you have the dependencies installed, you can build Zed using [Cargo](https://doc.rust-lang.org/cargo/).